This is an opinion. Not even a shower thought, but something that I just realized I could express succinctly.

I’m a TUI/CLI person. I look first for CLI programs, and only if I don’t find a way to do it in a shell do I look at GUI alternatives.

I’m also a tiling WM person. I used i3 for several years, and then bspwm for a hot minute, and for nearly a year now have been in herbstluftwm. I’m at a point where hlwm not running on Wayland is the main reason I’m not on Wayland.

But at one point, before discovering the joys of tiling, I was a big KDE fan. So it’s been interesting to find myself skipping Qt apps in favor of GTK apps when I have to use GUI apps; and just now I realized why:

When you pull a GTK app, only rarely does it link in a bunch of Gnome dependencies; when it does, it’s usually pretty obvious in the name or description… “X for Gnome” or some such. But Qt apps are really bad about hooking in and pulling a bunch of KDE dependencies, launching KDE services, and generally trying to turn your WM into KDE, that I’ve learned to just avoid them. There’s no reason for them to, unless it’s because the KDE libraries provide so much functionality that isn’t in the core Qt libraries.

Anyway, it just occurred to me why I have such a negative knee-jerk reaction to apps with Qt dependencies; I literally just filter them out as I’m scanning package lists.

I like Qt; I don’t like that most Qt apps also depend on KDE libraries.

  • TootSweet@lemmy.world
    3·
    6 days ago

    Honestly, I don’t like GTK apps either. I dislike them less than Qt apps for the same reasons you give. But GTK stuff is still really heavy and bulky and pulls in a lot of dependencies even if it’s not quite so bad as Qt stuff.

    When I can, I use apps that just depend on xlib or (even better) xcb. I’m a huge fan of suckless software, for instance. (Well, like you, when I can, I use a CLI program. But if there just isn’t a reasonable way to do something without a GUI, xlib/xcb is the way I prefer to go. But that isn’t often an option. Like, if you want a full-featured browser, it’s GTK whether it’s Firefox or Chromium.)

    I did make the jump to a Wayland compositor. (Sway. It’s as close to a drop-in replacement for i3+X11 as you can get.) So I guess even better than xlib/xcb would be the Wayland library. But in most cases I’d rather use X programs that are in my distro’s repositories than go outside of my distro’s repositories to use Wayland equivalents. (Like, I use “dmenu” because there isn’t a Wayland equivalent in the Arch repository. I am specifically in the process of switching from Arch to Gentoo, though, so it’s very possible that could change things moving forward.)

    Also, just because it’s apropos, I have literally written my own domain-specific language just so I could avoid using a GUI for one specific use case. Lol.