4 ms·
What's Red Hat got to do with this? Sure, they're a big GNOME contributor, but so is Canonical or Purism or Endless or, until recently, System76.
by sph 4y ago
What's Red Hat got to do with this? Sure, they're a big GNOME contributor, but so is Canonical or Purism or Endless or, until recently, System76.
- traverseda 4y agoAnd that's always the rub, isn't it? It's next to impossible to prove that most of the people in key decision making positions work for Redhat or are Redhat alumni.
- UI_at_80x24 4y agoRedhat is the main force that created systemd. And so their heavy-handedness into Wayland isn't surprising.
- sph 4y agoThat's a complete non sequitur. They mishandled A so necessarily they must have mishandled B as well. What kinda argument is that? And systemd is controversial in that a vocal minority says it was a disaster. I don't think it is, definitely not compared to Wayland.
- throwaway09223 4y agoHave you ever worked with RedHat? This is just how they are, across the board. (And maybe now we should be saying the way IBM is, who's history is even worse...) > And systemd is controversial in that a vocal minority says it was a disaster. Not a minority, and some of the loudest voices are the experts whos opinions matter most. I am one such expert. Most technical people I speak with about systemd are largely ignorant as to the design considerations.
- kaba0 4y agoYeah, no. Most actual experts very much prefer systemd due to it actually solving the problems inherent in booting up a system with all the services, and resolving the dependencies between them, instead of just being hacky bash scripts that only work on a single machine (if at all). The only people who have problem with systemd is “old-timers” that just refuse to learn anything new, and just blindly believe that the old status quo was better.
- throwaway09223 4y agoThat's the kind of attitude I often see from people who have never spent time debugging a dependency resolution issue in startup actions. People who do not have significant experience in running large scale, reliable systems. People with a desktop focus, who know little about systems internals. Engineering reliable systems often means reducing complexity. A major unaddressed complaint regarding systemd is that there actually isn't a need for dependency resolution during startup, at all. Dependency resolution is very complex and introducing it makes testing changes far more difficult. It is not a desirable feature for most server applications where reducing complexity and increasing operational visibility take precedence. > The only people who have problem with systemd is “old-timers” You may be confusing experience with age. The two are related but they are not the same. > that just refuse to learn anything new, and just blindly believe that the old status quo was better. This is just silly. There are all sorts of wonderful features related to containerization, cgroups for job control, structured invocation for processes, etc. The primary issue with systemd isn't that any of these features are bad. The issue is that they have been conflated in a mostly unspecified, monolithic system which discourages composition, inspection, and simplified operation. It's a big ball of mud architecture. You can't use the service invocation components standalone. You can't use the RC components standalone. You can't use the init components standalone. All of these things should be possible, but aren't, and that is the core issue. https://en.wikipedia.org/wiki/Big_ball_of_mud https://en.wikipedia.org/wiki/Big_ball_of_mud
- kaba0 4y agoThanks for the level-headed answer, I’m sorry I lost my cool there, but all too often one can run into Wayland/systemd-haters who are like absolutely unreasonable. What I compare systemd to is the previous iterations of linux init systems, and compared to them it is a huge positive change in my, and most of the linux world’s opinion (it was voted on multiple times in probably the most democratic process at debian, was decided independently at several other distro). It solves real problems (e.g. pre-disk mount logging) in a relatively modular way, and I think we should cut some slack here, because often times in complex problem domains a monolith is the correct choice. Multiple different tools will actually result in more complexity due to coordination, and I would go as far as that was part of the problem with previous init systems. May I ask you what would be your preferred solution in place of dependency resolution at runtime then? I do agree that it is “one more moving part”, I just fail to see how else could it work.
- hasperdi 4y agoFeel free to bring a better solution than systemd. Talk is easy, building something that works for the majority is hard. And one thing for sure is that not everyone will be pleased
- traverseda 4y agoOpenRC
- sph 4y agoHaven't seen any of my clients use it in production yet.
- traverseda 4y agoNo one ever got fired for buying IBM. But also you probably have used an openrc based distro if you've used docker, as alpine linux is very common.