I wrote this little piece originally on June 25, 2013 but decided not to push the publish button because it is incendiary, in more of one sense. But…
Systemd is truly a remarkable piece of technology. In the beginning I was skeptic for two reasons:
a.) I tend to orthodoxy when it comes to the core. I started using old skool init more than 20 years ago and it was with *real UNIX®*; at some point I even deemed SysV init style startup scripts the work of the devil. Ha! Like I miss BSD 4.2 init scripts! Everything mashed up in one single 5000 line shell script, *shudder*. Before I go tangential into a rant that is truly for another day, let me say this: All those weenies that say “FreeBSD start up scripts are the simplest and coolest thing since sliced bread” are a bunch of Christmas geese.
b.) I’ve my share of battle scars with “advanced” init systems. Ever had to write a startup script for HP-UX? AIX? What about that horrid abomination Sun Microsystems (R.I.P.) invented for Solaris (their SysVR4/BSD FrankenUNIX), startup scripts written in a horrible dialect of XML? Honestly, I suspect SMF was written in the midddle of a Colt 45 and crack brogrammer frat binge.
Then when Canonical pulled Upstart out of the hat (or may I say, arse?), I certainly put attention. I was already a user of Ubuntu, though not a convert. I had the chance to exchange a couple of mails with Shuttleworth when the the planning and design of the PPA system was in swing and he came accross as a narcissistic know-it-all. In fact, I was vindicated some year later when the man had to do exactly what I told him: People need the option to have several PPAs under the same account particularly if they are a project that hosts in Launchpad. There and then I decided I was not invested enough in Ubuntu nor would I be ever. I just kept using it because it was the best GNOME experience at the time. I’d moved to Fedora right there and then but it was still a POS.