Windows-think and systemd (Was: Something completely unrelated to what we're yapping about now)

In article <vj16j0$30r12$1@dont-email.me>,  <Muttley@dastardlyhq.com> wrote:
...

What would you say systemd does that is not related to that?

>
Networking, including DNS
Graphics
Logging
systemd-boot
>
Basically init should start the system, maintain some the running of
some essential daemons and then leave well alone.

I agree with you.  But it underscores a major difference between two very
different ways of thinking about computing, which can be described as
"Unix-think" vs. "Windows-think".

systemd represents nothing so much as the bringing of "Windows-think" to Unix.

If one embraces "Windows-think", then systemd makes complete sense.

In fact, systemd is a lot of like the original goal of MS's "dot net",
which was to put a solid wall between the applications programmer and the
actual operating system.

--
If Jeb is  Charlie Brown kicking a football-pulled-away, Mitt  is a '50s
housewife with a  black eye who insists to her  friends the roast wasn't
dry.