Smurfix

They knew that the target had nearly half a million [child ab]users.

That's sufficient motivation right there.

The problem is that once you have the infrastructure you can go after, well, any other random Tor onion service you damn well please, all with a minimum of judical oversight (if any).

Well, Ok, so the main thing that's good about it is that it's dead easy to start a goroutine. But that's actually bad, just like randomly jumping to any piece of code whatsoever is bad in in a procedural language.

Read the Structured Concurrency notes (https://vorpus.org/blog/notes-on-structured-concurrency-or-g...) for the reasons why.

How the heck should a library author know whether an error is recoverable or not? In many situations that depends entirely on the caller.

Not-so-contrived example: a config options contains a value that leads to a division by zero in some library I'm using. I don't want that to crash my whole program, I want to tell the user "hey this part didn't work" but be able to continue with the other parts.

Without writing a ton of boilerplate code.

You mean, like systemd?

Of course the tests are tested – by the code they're covering, which is also covered by other tests.

People can get by with zero LIDARs. There's no reason why autonomous cars couldn't. The real problems are elsewhere (emergency vehicles, ambiguous situations, construction, …). We'll need operators on standby for a looong time still. Good luck driving in areas without decent fast cell networking.

Dudette, actually. Pay attention. :-P

People still don' (want to) understand software.