Setuping services has been a pain for 15 years for me. Then with systemd it was suddenly easy.
Detractors keep repeating systemd sucks, but that this point, Debian and Fedora apparently decided it was good enough. And I never heard an end user complain.
I don't know if I qualify as an "end user" to you, but I definitely have complaints. I started with an open mind about systemd, because I'm not so attached to any init system in general. So my issue is not that systemd is a monolith or breaks with tradition (sysv init scripts were also a hot mess). My problem is that systemd looks and acts like a freshly written proof of concept that needs to be polished up, but when you dig in to debug a problem you're having, you inevitably end up at bug reports that condescendingly defend the current state of affairs as desired behavior.
"Your issue is user error, because systemd doesn't provide the logical guarantee you want, and adding a hook is outside the scope of systemd." I've run into several instances of this, the worse one being around unit ordering and network interfaces. I eventually solved it with a hack service that put 'sleep 90' between network.target and network-online.target. So much for that startup parallelism.
Another issue is that a dependency loop will cause it to just randomly drop units. There's no insight into this until you notice it happening and go digging. In the abstract, yes there is nothing else systemd could do apart from refuse to boot. Except the problem has only been dragged into the abstract by using a configuration model that punts on real world concerns.
Both of these are exacerbated by magic processes that half-parse crypttab/fstab/interfaces to create runtime units. I don't know if these are from Debian or the upstream. But if the systemd way is better, why haven't those been fully moved to native systemd?
That's not how I remember it. Fedora was pushed to adoption (thread starter characterises it as an internal "power play"), and Debian was presented a fait accompli (article summarises Russ Allbery with "[not] systemd-vs-the-alternatives, but how-much-of-systemd").
> And I never heard an end user complain.
This is ridiculous! I can also claim the world is always dark when I shut my eyes.
Linux mailing lists are full with complaints. A recurring one was an error message that suggests running a command as remedy, only for that command to also error out. (The remedy was formulated wrong.) By then, systemd already had a version number in the hundreds.
The article did a good job articulating that the "end users" of an init system aren't sysadmins, they're distro maintainers. If most distros have switched then it must make things better for them.
The problem, of course, being that for most init systems the "end users" are the distro maintainers but for systemd, because it spreads itself into so many other things, it also impacts the sysadmins and the upstream third party package developers. Who then complain about it and are met with "it was good enough for Debian and Fedora" even though they aren't the ones complaining.
Exactly, my biggest problem with the systemd complainers is that it's all kind of abstract things, like it's not the Unix philosophy, which in practice doesn't mean much and certainly doesn't automatically mean it's a bad thing.
SysVinit was a horrible, inconsistent mess of bash scripts of per-individual-developer variations in quality and not insignificant variations between distros, or even individual services within the same disto, I wouldn't hold that as the cornerstone of the Unix philosophy, that is if one's intention is to paint it in a positive light.
> SystemD feels like the new grad hire who decided the first thing the would do after joining — the opening power play — is to convince the PHB we should rewrite everything in Haskell.
I've seen this scenario played out, and it always fails. The product never ships, of ships in such a bad shape the users have a terrible user experience.
That's not what happened with systemd. It shipped. And after a few iterations, it actually provided a better user experience.
I don't know about sysadmins, but as a simple end user of Ubuntu, systemd is the best user experience I ever had for what matters to me: setuping my services.
It's quite easy to create your unit files, declare service dependencies, stop, restart, and so on. It's declarative, conf is reasonably straighforward to read an understand, documentation is there, and my system boot is stable on laptop and on my servers.
Maybe for "advanced case X", there is problem. Apparently, a lot of power users say there is. But I also know the FOSS community has some people advocating purity over practicality, don't care much about the people with less skills than them, don't understand user friendliness or will fight for their ego. So I have no way to be sure if the problem is real, or just another free software drama.
But at this point I don't care: for the average Joe like me, it's great, and I'm very happy it has been chosen by Centos and Debian as the default.
Apparently nobody in the entire history of init system have managed to provide something decent for, you know, initializing the system. I never heard a herd of devs claiming that one is the fantastic, and they were all terrible to use when I tried.
Well, I don't care for choice in my init system. I want it to work.
so what should be done, in your opinion, if it works very well for 51% of people, good enough for 48% and breaks the work flow of 1%?
easiest answer is to say get rid of the inter-dependencies, but that's throwing money and time at a problem affecting 1% of users, at no benefit to the rest. Maybe it's still the right answer, but who's to pick up the slack?
Nobody can setup a list of allowed topics, controversies or debates for society without destroying its ability to grow: any rule will eventually lead to censor a valid point.
20 years ago, when you talked about mass surveillance, you were a paranoid conspirationist or a crook.
70 years ago, when spoke against the vietnam war, you were anti-patriotic or a communist.
Not to mention we can be wrong now, or right now but wrong in the future.
I concur, this book is a terrible way to introduce anybody to Python.
I imagine they want to teach general programming skills, and hence want to give you a "way to think" that is low level enough to let you work with any language, using Python as a pseudo-code to demonstrate it.
This approach is doomed to fail.
It's much better to teach the language properly, then introduce other languages as a comparison point, if this is what you want.
I don't get the stellar reputation of this text, maybe it was great when it was written for Scheme, but as-is, I can't see most of my students even finding the motivation to reading it.
To disagree with you, I took the Python version of UCB's CS61A and I learned quite a lot (especially coming from a non-programming background). Perhaps other forms of SICP are better, but CS61A was a really enjoyable course overall and was part of the reason I decided to switch majors to Computer Science.
I can't understand how time would flow differently depending of your speed.
I don't get why C is a constant no matter the referential, for any other object the speed is relative to your referential. I just don't see how those 2 are compatible.
Ok, so the dev who knows 5 languages, a bit about database, git and sysadmin has been hired to do one job. On this job, one must learn the entire stack, including docker, in a few months, while still reaching the deadline.
The dev won't be paid more.
The company won't spend more resources.
Time is short, talent scarce, customers in a hurry.
> My view is that people here are far too trusting of those in authority, and in particular counter-terrorist police and security services personnel.
I always though "brainwashed by TV" was an exaggeration. But the more I discuss with people, the more I realize they think the police/hospital/army/court works like on TV.
E.G: they expect that if there is a murder, an NCIS like team with try to find the murderer, or if they get strange like disease, some Dr House will be assigned to find the solution, or that judge are impartial and mayors are competent to deal with the solutions their city require. The reality is that people are average human being with limited resources everywhere. They are lazy, have ego, have a small budget, are tired, have an agenda, have bosses and politics, etc.
"authority, and in particular counter-terrorist police and security services personnel" is no different.
Giving full control to one company of the thing that can be published, discovered an install is a receipe for all what's wrong with monocultures.
Don't get me wrong, the app store is a fine service. And that it's the default experience for beginners is a reasonable compromise.
But assuming it as the only channel is like a hospital refusing to heal people that eat processed meat because WHO declared it carcinogen.