Good teams don't blame individuals. You can praise individuals, but you take blame as a team.
Hopefully at least two people reviewed the commit before it was put into production. Someone set up the post-launch smoke-tests/api-test-suits. Someone built the CI/CD-system. Etc etc.
My point is, it is rarely a single individuals fault when something at this scale goes down.
Philae did send data for three days (unless i miss-remember). Knowing where that data was taken helps put it into context. So quite important for the mission.
Why do you assume this was illegal in Sweden in the late nineties? In Sweden, downloading of IP was illegalized 2005-06-01. Before that it was only illegal to spread digital IP...
To my knowledge, Erlang uses a cooperative scheduler. The process itself counts downs its reductions and yields when it is time. The programmer can call erlang:yield() to do this before time if he wants. Calling something like receive will also yield. I guess it comes down to definitions, but since Erlang is said to have only soft real-time (as opposed to hard real-time) properties, this makes more sense. The schedulers doesn't give any guarantees as to when a process gets to run and the scheduler never really preempts a process. Again, to my knowledge.