That's a great point, and has almost nothing to do with Kessler Syndrome. But what can I say? I live near a city where the leaders of a few nations decided it would be fun to test the effects of fallout by releasing radioactive dust over it. Aluminum oxide is pretty benign, comparatively.
Certainly, the consequences of our actions need to be considered, but let's stick to the legitimate ones, such as what you listed, and not the highly improbable ones such as Kessler Syndrome.
Debris from a collision can be flung in all directions, including higher orbits.
Possible, but not at all likely. The joy of orbits are they're pretty predictable because after the energy is applied the object just keeps following a path. To get a higher circular orbit would require deceleration at the right point to stabilize it. If this doesn't happen, and it doesn't in a collision, you will have a new orbit that will more or less pass through the altitude of the impact. So while it may have a higher apogee, it will have a lower perigee, which means it will suffer more drag due to more atmosphere. So the vast majority of debris from the collision of a LEO satellite collision will naturally deorbit, possibly faster than if the satellite hadn't just become inert in its orbit.
The low orbits that need to be constantly maintained or they naturally deorbit are the exact opposite of Kessler Syndrome. If every Starlink satellite was to disintegrate right now, the majority of the debris would be gone in 5 years.
There was a story about a researcher using evolving algorithms to build more efficient systems on FPGAs. One of the weird shortcuts was some system that normally used a clock circuit, but none was available, and it made a dead-end circuit the would give a electric pulse when used, giving it a makeshift clock circuit. The big problem was that better efficiency often used quirks of the specific board, and his next step was to start testing the results on multiple FPGAs and using the overall fitness to get past that quirk/shortcut.
Pretty sure this was before 2010. Found a possible link from 2001.
So, "nuclear test und an uninhibited island" next?
Un inhabited?
Edit: apparently you can't have partial words italicized.
Summarize that sentence into a thumbs up or thumbs down emoji.
Pretty much everything you said is incorrect, except for the article age. Valetudo literally wrote software that does this on multiple models locally, including mapping. The response of the manufacturers whose models were capable of this was to release new versions where this wasn't an option. As for servers and local control, there are a number of solutions for those with the knowledge and hardware to set it up, and the only thing stopping robovac companies from supporting this is (less) money.
We could still live in caves, but most of us have chosen not to. I'm personally of the opinion that every advancement that gives you more time to do things that are important to you are worth it. This doesn't mean inviting every piece of spyware some company tries to thrust upon me is acceptable, either.
That's not really how orbits work. Unless there is a stabilizing burn or very unusual conditions the debris will have an eccentric orbit, going both lower and higher than the impact point. And passing below the orbits of the starlink satellites will expose them to even more atmosphere than they will be at the starlink orbit, so their orbits will decay faster than their apogee would suggest. Sure, some will experience the right conditions to put them in an orbit such that the perigee is at the altitude of the starlink orbits or even higher, but the vast majority will not.
This does not preclude carelessness or malice causing impacts, the launch in question being the former and China's satellite destruction previously being the latter. Do you think Starlink isn't releasing their orbital paths to other launch organizations? And that net is generally very predictable. Any deviation from the existing orbit is done at the expense of the lifespan of the satellite and while there are a lot of those satellites, there's far more empty space between them. The kind of planning that rocket launches normally get is more than enough to hit those windows, along with the other windows rocket launches normally have to hit.