https://blogs.gnome.org/adrianvovk/2025/06/10/gnome-systemd-dependencies/
Burn in hell!
Wow. Looking at the stuff he's written under "So what should distros without systemd do?", he could've just spelled it out: you'll need your own fork.
Non-systemd distros will need "implementations" and "bridges" and what not. So we'd have to implement systemd "features" to keep away from systemd? I'd rather keep away from Gnome from now on!
But isn't it nice that he's "helping out" with a temporary alternate code path? Why is the whole section even there? Feels like he's mocking non-systemd users.
see also https://www.osnews.com/story/142551/gnome-adds-dependencies-on-systemd-lots-of-work-to-do-for-systemd-less-environments/
Nothing new under the sun, Red Hat has been trying to EEE Linux for a long time (https://lists.freedesktop.org/archives/systemd-devel/2014-May/019657.html) so please allow me to politely extend an unconcerned middle finger. As for the "So what should distros without systemd do?" rhetorical question, the answer is proverbially obvious: "we don't offer Gnome - we won't offer Gnome, duh".
Extra points to "Thom Holwerda" for being really spiteful (or happy?) about this change?!
Gnome pushed itself to irrelevance years ago, so I can't imagine many people "jumping up and down"...
I'd be upset if Gnome was any good.
Related https://news.itsfoss.com/fedora-43-wayland-only/
With kind of weird decision making https://pagure.io/fesco/issue/3408?ref=news.itsfoss.com
The change proposal was pitched by Neal Gompa of the FESCo, who mentioned that:
Can't say I'm surprised. Honestly the only thing that's now lacking is if they switch GTK and gnome to rust and we'll come full circle.
We already have a few checklists done:
Trying to enforce gnome's standards on everyone or make it difficult to work with them ✓
Infect soystemd with anywhere and everywhere even if it's not even remotely relevant ✓
Shutting down potential competition such as Xorg (or rather XLibre now) ✓
Canonical is in on it too.
Replacing time-tested coreutils with bleeding edge software (not even version 1.0 but 0.1.0) uutils. ✓
Snaps ✓
PostMarketOS also went to use systemd by default, because of all the needed wrappers needed (at least a valid reason)
https://postmarketos.org/blog/2024/03/05/adding-systemd/
It's kind of unfortunate because upstream GNOME has accepted plenty of my elogind/systemd-optional patches before. I think gnome-session's planned changes are the one thing that might affect us. We may or may not have to drop GDM. Depends on how it shakes out.
window maker is looking like a smarter and smarter choice with each passing year
What the fuck is that.... does the damn mouse work? Cut and Paste? Keyboard?
We have been using the "Wayland Experience" since xerox Park...
https://www.youtube.com/watch?v=TLV4_xaYynY
I am sick of the marketing crap being poured onto the Linux ecosystem to justify the unexceptionable.
It's funny how it all accelerates, ain't it? It's like we all were right from the start, but remember we're delusional ones...
But you know, this is exactly how things are right now. If you’re running OpenRC (which gentoo is basically abandoning, especially with how google has taken over some of the top roles) you’re still using several forked systemd components like eudev, elogind, etmpfiles, esysusers, etc. What we really need as a community is an easier, more automated way to replace those. I’d assume that’s already in the works, because, as stated above, they clearly don’t like our choice.
Given that newer versions of GTK are worse in many ways than older ones, it may make sense to port Xfce (or Mate) to QT, or fork an earlier version of GTK.
My most recent irritation is preview images not resizing when the modal dialogs are resized. IIRC the recommended fix is to search for the file in your file manager since you have the name of the file right there in the file open dialog. Literally a step back to the 1990s or maybe earlier.
I remember experiencing similar annoyances in the past 13 years, but I can't recall what they were.
I'd rather have a GTK3 fork that'd inject itself and behave like normal GTK, but with stabilised API and without being ever updated to whatever the fuck GNOMIES what it to be...
More like "whatever the jackoffs paying Gnome rodents to be whatever they want it to be."
Oh, no! What are we ever gonna do without the Wayland compositor that adamantly refuses to implement the Wayand protocols that people want?
I am personally using KDE + Wayland + dinit and it works much better than X did at any point since the mid-2000s when I started using it. So yes.
Also, screw GNOME. Who needs them anyway? I spun up a virtualbox Arch install to see what it looks like and god DAMN they actually made it worse.
- The new text editor is worse than Windows 95 notepad.exe
- The new terminal looks like something I could code in 5 hours. "professional quality software" from IBM/RedHat
In my eyes GNOME as a project is both hostile and unpredictable to the point where it wouldn't be unjust for forward thinking distributions to just outright remove the desktop proper and refuse to package it. I mean how irrational would it be to Just Say No when upstream are a bunch of pedantic children who don't listen to any real feedback?
You forgot the part where GNOME developers are the same people that work on various mainstream distro as packagers. It's not easy to cut the parasite off when it's host was already replaced by parasite.
Wait, you mean the exact same thing that happened with systemd remove-trailing-space-commit-"developers"?