4 ms·
The point though is that there used to be a «Linux desktop» you could target before the Wayland transition. Fragmentation of an already small market segment is
by setopt 4mo ago
The point though is that there used to be a «Linux desktop» you could target before the Wayland transition. Fragmentation of an already small market segment is unfortunate.
- chadgpt3 4mo agoIt's KDE now. GNOME is the penguin that went to the mountains while KDE largely tries to be compatible with things that aren't KDE.
- setopt 4mo agoSure. I use KDE myself. I actually like the Gnome default UI/UX more, but I'm really not fond of their "our way or the highway" approach when it comes to customization and interoperability. KDE feels more in line with the true FOSS "spirit", and after a bit of customization, fits my needs better than Gnome.
- tuna74 4mo agoThere was not really for system utilities. Apps, sure, but not system utilities.
- setopt 4mo agoWhat do you refer to as system utilities? All the stuff now subsumed by SystemD?
- tuna74 4mo agoThings like input methods, certain accessibility functions, screen savers and similar things.
- MarsIronPI 4mo agoHuh? Fcitx and IBus both worked on GNOME and KDE as far as I'm aware. Now, Fcitx using QT and IBus using GTK helps them feel more native on KDE and GNOME respectively, but they would both work.
- tuna74 4mo agoDoesn't seem possible on Gnome and not very straightforward on other DEs according to the arch wiki: https://wiki.archlinux.org/title/Fcitx5#Integration https://wiki.archlinux.org/title/Fcitx5#Integration
- MarsIronPI 4mo agoIt seems to me that the issues on that page are Wayland-specific; anectotally, on my random X window manager works fine with Fcitx (except for Emacs, but that's probably Emacs' fault, not the IME protocol's).