@mjg59 itym 200 projects in a trenchcoat.
My minor involvement in the Debian TC on this topic was certainly enlightening. There is much to dislike about systemd, but even back then it was dramatically better in so many important ways than any of the alternatives.
@mjg59 but anyway, high disagree that there should be a singular "the core infrastructure" to begin with
variety and diversity is one of the things that make Linux appealing and broadly useable, harmonizing towards a monoculture ain't it imo
@mjg59 I agree, although I think there are some compounding factors that do make it more difficult in the current landscape, forcing such a (set of) undertakings to solve more of these problems At Once
but that's a thought that needs some more stewing instead of being blarfed out unfinished at 2AM :)
@shiz @mjg59 excessive variety and its fanatical zealots were what was holding linux/freedesktop back by decades.
having 300 ways to manage windows, 200 ways to configure system startup and 100 ways to configure the network is nerd masturbation. it does not a competitive real-world-able platform make
@valpackett Linux systems in all kinds of shapes and forms have been "competitive" in the real world since way before systemd came along, even if that were the only metric to care about
regardless, you'll understand I'm not very interested in further engaging in a discussion when the first reply is full of dramatical hyperbole and dismissal
@alwayscurious @valpackett @shiz @mjg59 This is false. While monogameous project grow fast in the longer run they are very toxic for the whole environment.
Like with browsers, when one engine dominates the web developers stop keeping to the W3C standards and just make it work with IE/Chrome. It's pathological.
We also need alternatives in case The Big Project goes bad (like Systemd right now accepting AI pull requests or adopting dangerous California law)
This is why we need competing standards for a healthy platform.
It's slower, but it's good (unless you want to move fast and break things like certain wealthy ketamine lover)
@shiz diversity is great until it starts slowing down usability. When the effort of hundreds of people are split to try to fix the same set of issues, I feel like everybody's wasting time.
(Of course, the general answer to this is that no, it's not *exactly* the same issue we're trying to fix, but it's often a little bit of a lie)
Those who don't like it may prefer the more traditional BSDs
๐
where the kernel and init system share the same source repository?
My point being that systemd forms the basis Linux userland in a way that makes the whole system feel more coherent, just like how BSDs have been described as more coherent.
@mjg59 I've never seen an init system that relied on awk to make all its scripts compatible, but even so, awk works.
On the other hand, software built with LLM-plagiarized code is *bad*, actually. https://mastodon.social/@kapualabs/116273857383339305