If you dont have hotplug hardware with its udev nonsense, and you don't have a GUI, and your users don't log in interactively to the OS, why do you need systemd and all its crap? init + an rc script to launch $YOUR_APP and you're done.
Of course Memedot has to trash Branson, a businessman, over Musk, a trendy-named dotcom guy with a penchant for electric cars.
The bastard child of a trashy hardware site (i.e. not Anandtech, maybe TH or one of the other lamer ones) and OSNews. Did they round out the article with meaningless, unlabelled graphs?
Agreed, game / set / match, and helping him use the advice you have given to teach the class as well, earns you extra points.
Even with points deducted for smugness...
You win 1 internets.
Believe it or not, I sincerely believe that this introduction was his way of eating the humble pie, in advance - prostrating himself at our altar and asking for help. We should give him a break!
Hooray, getting more plastic knockoff versions of things, produced by slaves (hint: Communism doesn't treat people kindly), with zero regard for the environment, and shipped halfway across the planet.
And that's the root of it. The socialist hatred of profit.
When those 3000 dudes come home, and go back through the major US airports, back to their families distributed across the country, and THEN spread the disease, it's going to be awesome.
Never wasting a good crisis, the President and administration will use this as an opportunity for massive federalization of health care and private sectore business.
As a RHEL server admin, the only thing I see systemd adding is complexity. Do a fresh install and compare it to RHEL5 or 6, and you have way more stuff running, new start/stop methods for init scripts, weird NTP replacements, and a bunch of stuff that you don't need. Then you go and install your app, or something like Postfix (because you're building a mail server). Why do you need parallel boot? udev hotpluggery? a "logind" process?
8 Catfish = 1 Octo-puss
