Fortunately such “new choices” get abandoned very quickly. Making new solution instead of improving existing ones is counterproductive. Unless there is a large legacy codebase. Smart people have invented Unix principles to avoid that.

Not really. Best Foss projects do not always thrive. Git wasn’t really better than mercurial. But it had happened to be published earlier, so it got wider adoption.

If you will create “next gen” desktop, you will just solve some problems of already existing ones and create your own. Maturity of software is far more important, than uniqueness. GNOME didn’t evolve into its current state for no reason.

Why do we invent new DEs instead of making proper settings app in already existing ones?

Fight for Americans’ fit bodies! Stop illegal oil production!

Wayland is like Busybox runit. Xorg is like SystemD.

Some seem to use Debian.

IMO the closest one.

Linux Libre makes Guix unusable on most hardware. It also requires much effort to configure. Learn scheme, how to use shepherD, etc.

It’s really cool, when automation tools create more problems than they actually solve.

There is really no reason to implement extensively audited runC in C, but the Dev only has the journey, no goals.

Ncmcpp, MPV with scripts

Not really. Void, alpine, gentoo are the only usable ones(besides non-systemd forks of arch and Debian). These are the only ones maintaining enough packages, providing enough documentation, not being just poorly maintained forks of X distro.

Openrc…

Misconfiguration is possible in any software. It’s not specific to sysvinit or systemd-init. Selinux was created to solve this.

I deleted it. No need for two almost identical posts to exist.

the added difficulties of making it system agnostic did not compensated for the low user base

• 2003: Udev was launched, providing support for musl, non-systemd distros, and others.
• 2004: NetworkManager was launched, with Udev as a crucial dependency.
• 2006: Dbus was created without dependencies on distro-specific packages.
• 2009: Dbus becomes a dependency for NetworkManager.
• 2010: Red Hat introduces systemd, with core components including logind, journald, and timers.
• 2012: Developers made udev less compatible with old kernels, musl-based, and non-systemd Linux distros by merging it with systemd. You can find more information about this here: https://lwn.net/Articles/490413, https://lwn.net/Articles/529314/
• 2017: PipeWire was launched, with logind as a dependency.
• 2017: Reimplementations of the bus protocol called dbus-broker were launched. Its compatibility launcher requires systemd.
• 2020: After systemd had already been adopted by all major distros, systemd-tmpfiles gained the ability to be built as a standalone executable.
• 2022: WirePlumber was launched, with pipewire as a hard dependency.

Looks like Red Hat makes everything they can systemd-dependent. Including Gnome.

Compare it to vulnerabilities found in SysVinit, which was as common as systemd-init is now. There were no similar bugs, that would allow crashing an entire system just by executing a single command.

There is an example: https://www.agwa.name/blog/post/how_to_crash_systemd_in_one_tweet

We know.