a guy from Scotland punched me once...

I bet you don't eat hagis...
;)

Oddly, I love the stuff [haggis]... ;)
Comparing any project to any other is a bad thing -- everything ought to stand on its own merit.

That I can agree with without reservation and withdraw the comparison. Mia Culpa

He probably should have hit you harder

He won't and can't. He's not a terrorist.

:D
Indeed, if I were a terrorist he'd have kicked me so hard in the genitals that he damaged his own tendons...

OK, either you're making a joke I'm not getting or you didn't get the joke I made. I meant if he'd hit him harder he wouldn't like hagis, not that somebody needs to hit 273 really hard.
Sorry for any confusion, fortunately 273 got it.

It was a joke, positive of course.

Cool, I'm normally on the other end of peoples jokes, this is refreshing.

I think that you would be hard-pressed to come up with a bibliography to support that position. :rolleyes:

Nevertheless – it may be said that both projects are serious attempts to accommodate various aspects of the profound(!) changes that have occurred in the world of computer hardware, as well as in the deployment situations in which hardware now finds itself.

"This being Linux, you can make your own personal decisions with regard to your systems. However, Linux is now being deployed into an astonishing number of very different scenarios. Your situation is now only one of a great many.

Sometimes, the best thing to do with an old and venerable software system is "to replace it." Unix was first put on the table in the 1970's, and since I was there, I can attest that the design decisions which were made in those days have no relevance today. ("Not in our wildest dreams could we have ever ... although it sure-the-hell has been fun ... etc.") Much the same situation has also happened with regards to graphics. The underlying architecture of a "laptop" or "desktop" has zero-nada-zero to do with that of "a phone." And, who knows what might come next.

"It's okay to supersede something. Really ..." :)

Bibliography? Dude I can barely read, I think you're setting the bar way to high....People who see the problem don't write books about it, they just shake their heads.
Perhaps you meant to say "computer software" since that's what virtualization is. Things haven't changed much in the server world since they tossed the pizza boxes in the dumpsters and slid the blades on racks with high speed backbones. That said, you can control the boot process of a virtual machine the same way you can a physical one.
... with something better.
And by better, I mean cheaper to run, not having a more convenient API.

The one question I've always wanted to ask someone who is knowledgeable about the thinking behind systemd is, since we have dbus which spawns at boot, and systemd doesn't do anythin dbus couldn't do past that point (we can control the boot process any number of ways so let's skip that part) why didn't they build out dbus instead of building a brand new service? Now we have two demonic processes, and a churning host of their worker threads, running constantly.

EDIT:
On second reading, this sounds somewhat irritated with you and systemd, I'm neither, actually, just more curious as to why they didn't go with what would appear to be the default choice.
Couldn't agree more. That's what pays my bills so devil take the man who cries "hold!"... ;)