I could agree with that, my emphasis added. It seems like a drastic reduction from the charge you originally leveled. 'Email' is actually a fairly complicated thing requiring a fairly complicated toolset, after all. You mention an editor as something different (and it is) but no email program could function without some editor at least. And usenet is extremely similar to email in terms of the toolset required. You *could* do all this by piping different tools together on the fly and you *could* argue that's the only twue unix way but it's stretching a pretty thin point way too far when you equate Alpine with Outlook.
I was a member of a church where I routinely received death threats from other members. Since I was the "low bar" for spirituality that other members compared themselves (i.e., "I may be in sin, but I'm not a sinner like THAT guy"), my repentenance always made some members angry because I raised the bar for them. The church leadership routinely dismissed my complaints and I was frequently called a liar.
That changed when I confronted members threatening me by looking them in the eyes and telling them that I would kill in self-defense. These members thought I was bluffing and backed off when I invited them to take it outside. The leadership took my threat seriously, as I was scaring the crap out of people. I was eventually kicked out of the church and told to get counseling.
CO2's atmospheric lifetime is something like 1,000 years. How come those who fret about the longevity of nuclear waste never seem to talk about this? With fast reactors that burn the actinides (including plutonium) as fuel, the remaining fission products decay to the level of the original uranium ore (while being considerably more compact) in only a few hundred years, much less than the atmospheric lifetime of CO2.
The hype about "carbon capture" is just that -- hype. But it serves one useful purpose: its utter impracticality shows just how minor the nuclear waste "problem" is by comparison.
Systemd is not like that. It takes over everything and wont give it back, even when it pretends to. For instance, it logs in binary. IF you read the docs and throw the right switches, you CAN get it to put out text logs. Ok, so no big deal, just flip the switch, right?
No. The main reason we want text logs is because of what happens when the system crashes. Even if you flip the switch, systemd is still logging in binary and just writing out a text version to make you happy, a few milliseconds later. So this fix is, well, not totally pointless, it does at least make the logs manipulable using standard tools again. Except on occasions when you really need to read them.