Live data from Hacker News

Introducing stronger dependencies on systemd

blogs.gnome.org

11–20 of 179 posts

Re: Introducing stronger dependencies on systemd

#12
post #7

[flagged]

What do you recommend instead?

With systemD, the alternatives have a curve because so much IBM money and monopolization has gone into it. But systems using OpenRC(alpine) or SysV(MX linux, Devuan) work great in my experience. there are other init systems like runit (void linux) also seem to work great too, I just haven't used them.

As for desktop environments, the choice is very easy. Because there are simply better options. For normal users, I always suggest KDE Plasma or XFCE, Cosmic is still in development but looks very promising, cinnamon also looks great, but I don't use it (I know it's a gnome2 fork). But for power users, the choice of WMs are pretty trivial. i3, xmonad, qtile, niri, leftwm, etc.

The experience of using a WM instead of a full DE is incomparable for professional and power users. That is why I LOVE XFCE because it is modular. you can use parts of the XFCE ecosystem in any WM (power manager, theme manager, file manager etc.) or just replace xfce wm with your WM of choice (although I don't recommend this).

Re: Introducing stronger dependencies on systemd

#14
post #3

This is a good move. Without having endless resources keeping the codebase small and focused just makes sense. I know it's going to be painful for non-Linux users but volunteer devs can't be expected to cover all bases.

They do have endless resources. They are an IBM company. If people choose to work for IBM without getting payed, that's kind of their problem.

gnome is an IBM company?

Re: Introducing stronger dependencies on systemd

#15
post #5

What is Gnomes market share like these days? It used to be the de facto FOSS desktop in the GNOME 2.x days but things changed with the release of Gnome 3 and I’ve not really noticed Gnome ever bounce back since.

Every time there is an interview of some startup and they show the offices with a glimpse of a monitor, it's always Ubuntu. Running gnome.

Also a few people I know, if they used Linux on a desktop it was Ubuntu.

Don't know anyone using KDE, steam deck being the only exception.

So from a personal perspective, if it's Linux on the desktop, it's gnome.

Re: Introducing stronger dependencies on systemd

#16
post #7

[flagged]

What do you recommend instead?

Not parent, but...

There is a rich world of window managers, if you run a proper distro with X11. IceWM for example is a great building block for your own desktop, you can combine it with the file manager you prefer, or use a terminal instead for that, use it with a dock, tray and a helper like conky instead of the default task bar. The capabilities of real WMs are great, to pin windows (permanently), have workspaces, give overviews - and that's before going into the auto tiling direction.

But that's only if you want to have something custom. Otherwise KDE would be the default alternative to Gnome, then XFCE or LXQT for smaller desktop environments.

Re: Introducing stronger dependencies on systemd

#17
post #5

What is Gnomes market share like these days? It used to be the de facto FOSS desktop in the GNOME 2.x days but things changed with the release of Gnome 3 and I’ve not really noticed Gnome ever bounce back since.

who does even compete with Gnome ? it is the de facto default desktop in almost all notable distros. it just works, though it is far less customizable compared to KDE, it is far more stable -still only compared to KDE..

> it is far more stable -still only compared to KDE

Citation needed ;) I haven't seen any 'instability' in KDE since I switched from GNOME, and performance/snappiness of KDE is actually better.

Re: Introducing stronger dependencies on systemd

#18
This is the back-end plague which is everywhere in free software. The idea is that whatever "it" is, adding support for "it" is "just another back-end" . Take cairo for example, it has or had back-ends for gdk, win32, png, svg, html canvas, pdf, postscript, opengl, xlib, quartz, etc. Only a few of them are actually usable and support has been removed for several others over the years. The number of sound back-ends on Linux is uncountable: ALSA, OSS, OpenAl, PulseAudio, Jack, Esound, PipeWire... It's never "just another back-end" because every back-end needs continuous testing and maintenance.

Poettering when designing systemd wisely, WISELY decided to not go the back-end route. Other free software hackers learn the hard way that multiple back-ends are expensive and rarely worth the cost.

Re: Introducing stronger dependencies on systemd

#19
post #13
post #7

Earlier quoted context omitted.

What do you recommend instead?

Not parent, but I'd recommend you get a lay of the land and not trust rando's ramblings.

We are not lawyers. I don't care what their "parent" company is legally. In practice, IBM influences and affects every single decision of these projects/companies. So yes, It is their parent company. Just look at what they were doing to X11. Holding it's development back just to monopolize wayland more.
Post reply on HN