It costs a lot to get excess delta-v into orbit. It's HIGHLY unlikely that either of them would have much more delta-v than what is required to deorbit them. That would be way short of the amount required for intercept and even if you do happen to make it... what then?
I might be an old geezer at this point but I feel like the Slashdot from my youth would have phrased this as "A Stack Overflow..." as opposed to "Stack Overflow...".
I feel like editors nowadays a) have no clue what they are talking about b) are concerned with clicks over substance.
When you consider the cost of a potential data breach $9000 (for years worth of hard drives) is nothing. I love to hate 'the man' as much as the next guy but there is a time, a place, and a need for standardized destruction of data.
I dislike using Java for work ( mid-sized web applications) but when I've been forced to deal with Java code I have enjoyed being able to quickly understand what a developer was trying to do regardless of their level of expertise.
It's really good to have simple, slow-evoling, core elements to a language when it comes to learning, teaching, understanding, etc..
'OS-less' based system, sweet! Just think, we'll save a few seconds during the boot up process and it will only take hundreds of hours for our devs to code in assembly / binary! It's almost as efficient as the href-less anchor tag.
Sarcasm aside... there is something working as an OS it's just trimmed down to the bare minimum.
Also, check your damn summaries.
FFS... Situation A) Blame automatically applied to manufacturer : They send out another unit and sell the 'defective' unit as a refirb or B) They have the data from 'smart' sensor bitch and moan with shipper's lawyers over who is responsible for the damaged product after spending time review logs.
The only people who win with situation B) are the Goddamn lawyers.
This just seems like an instance of a coming up with a solution that costs more than the initial problem.