Recently I posted a gripe about `kitty`'s memory usage. This got me curious about memory usage of terminals in general, so I devised a test. It wasn't all that well controlled, but I did open eight different terminals on two different machines (one KDE/Wayland/Fedora 44 and one Openbox/X11/Debian 13, both amd64 with 16G of memory, recent kernels, etc.) and ran the same sequence of commands in all 16 terminals. I used `smem` to record the memory usage for the terminals, both right after they were opened and then after the sequence of commands was run. ==== Openbox / X11 / Debian 13 ==== PID Command Swap USS PSS RSS 115733 st 0 2592 3008 12788 115892 xterm 0 6808 7414 17732 114856 /usr/libexec/gnome-terminal 0 10252 14984 52836 115034 /usr/bin/kitten __atexit__ 0 19772 19783 21168 114615 alacritty 0 34224 43478 98396 115005 kitty 0 56376 66584 129180 115381 ptyxis 0 54760 67603 144640 PID Command Swap USS PSS RSS 115733 st 0 3396 3834 13780 115207 lxterminal 0 7800 11159 42656 115892 xterm 0 11640 12266 22748 114856 /usr/libexec/gnome-terminal 0 10692 15416 53340 115034 /usr/bin/kitten __atexit__ 0 21972 21983 23368 114615 alacritty 0 40188 49444 104408 115381 ptyxis 0 58252 71107 148316 115005 kitty 0 70716 80917 143568 ==== KDE / Wayland / Fedora 44 ==== PID Command Swap USS PSS RSS 30975 st 0 2924 3374 12832 31112 xterm 0 6460 6691 13204 30850 rxvt 0 8936 9440 19248 29259 /usr/libexec/gnome-terminal 0 12168 19005 53420 29417 /usr/bin/kitten __atexit__ 0 22852 22864 24464 29098 alacritty 0 25468 28837 73416 29401 kitty 0 46468 51520 105816 29690 ptyxis 0 73220 79204 141012 PID Command Swap USS PSS RSS 30975 st 0 3204 3820 13836 31112 xterm 0 9888 10119 16632 30850 rxvt 0 12872 13736 27096 29538 lxterminal 0 9824 15343 48804 29259 /usr/libexec/gnome-terminal 0 12660 19313 54056 29417 /usr/bin/kitten __atexit__ 0 22884 22896 24496 29098 alacritty 0 34188 37470 82580 29401 kitty 0 53048 58032 112936 29690 ptyxis 0 75060 81130 143284 The results are ... interesting: - I didn't think I would find a terminal with less memory use than `xterm` - I didn't think I would find a terminal that was more of memory hog than `kitty` (although if you add `kitten`'s memory usage, maybe it still wins) - I expected `gnome-terminal`'s memory usage to be in line with KDE's `ptyxis`, but `gnome-terminal` shows remarkably well in this test - the environment (Fedora vs Debian, Wayland vs X11) doesn't seem to have made much difference at all - of the terminals, `kitty` is the only one that can show pixel-perfect images with `timg` (that was one of the commands I ran) - `lxterminal` doesn't appear on either first recording, my mistake - `rxvt` was running but wasn't recorded properly on the X11 machine, don't know why - all of these terminals (and `smem`) are available from the distro repos - both Fedora and Debian I think I'm going to try out `st` some more. Not that my machines are that badly memory-constrained, but if it meets my other needs, why not use the least memory-hungry terminal? Since I commonly have about ten terminals running across 2-3 desktops, it adds up. If `st` doesn't work for me, I'm going to try out `gnome-terminal` some more. (I'm also likely to post this on my blog.) -- Giles https://www.gilesorr.com/ gilesorr@gmail.com
Giles Orr via Talk wrote on 2026-05-05 18:10:
- I expected `gnome-terminal`'s memory usage to be in line with KDE's `ptyxis`, but `gnome-terminal` shows remarkably well in this test
Would love to see how KDE's `konsole` compares - this is a very interesting test result.
(I'm also likely to post this on my blog.)
If you do, can you add in konsole? Thanks for this info Giles!
Here's an interesting thing ... I assumed `ptyxis` was the replacement for `konsole` because that's the default terminal used on my Fedora 44/KDE system. But when I ask DDG about `ptyxis`, all the results mention Gnome. Weird that a KDE system defaulted to it. Also ... what does that mean for `gnome-terminal`? The KDE system isn't totally default, it started at Fedora 41 with GNOME. I'm still surprised the KDE install didn't bring in and use `konsole`. I'll report back if I manage to update - no promises. On Wed, 6 May 2026 at 01:02, Ron via Talk <talk@lists.gtalug.org> wrote:
Giles Orr via Talk wrote on 2026-05-05 18:10:
- I expected `gnome-terminal`'s memory usage to be in line with KDE's `ptyxis`, but `gnome-terminal` shows remarkably well in this test
Would love to see how KDE's `konsole` compares - this is a very interesting test result.
(I'm also likely to post this on my blog.)
If you do, can you add in konsole?
Thanks for this info Giles!
-- Giles https://www.gilesorr.com/ gilesorr@gmail.com
Here's the whole thing as a blog post, with the Konsole info added. https://www.gilesorr.com/blog/linux-terminal-memory-usage.html On Wed, 6 May 2026 at 01:02, Ron via Talk <talk@lists.gtalug.org> wrote:
Giles Orr via Talk wrote on 2026-05-05 18:10:
- I expected `gnome-terminal`'s memory usage to be in line with KDE's `ptyxis`, but `gnome-terminal` shows remarkably well in this test
Would love to see how KDE's `konsole` compares - this is a very interesting test result.
(I'm also likely to post this on my blog.)
If you do, can you add in konsole?
Thanks for this info Giles! ------------------------------------ Description: GTALUG Talk Unsubscribe via Talk-unsubscribe@lists.gtalug.org Start a new thread: talk@lists.gtalug.org This message archived at https://lists.gtalug.org/archives/list/talk@lists.gtalug.org/message/ZEUM35U...
-- Giles https://www.gilesorr.com/ gilesorr@gmail.com
Giles Orr via Talk wrote on 2026-05-06 19:48:
Here's the whole thing as a blog post, with the Konsole info added.
https://www.gilesorr.com/blog/linux-terminal-memory-usage.html
Thanks. I had to try this `timg` since it works inside konsole, and "wow" it's really nifty. I had no idea this was possible, but sure is handy.
Ron wrote on 2026-05-06 20:32:
Giles Orr via Talk wrote on 2026-05-06 19:48:
Here's the whole thing as a blog post, with the Konsole info added.
https://www.gilesorr.com/blog/linux-terminal-memory-usage.html
Thanks.
I had to try this `timg` since it works inside konsole, and "wow" it's really nifty. I had no idea this was possible, but sure is handy.
Just tried it on a PDF and ... it worked! Didn't have to switch to file manager, navigate to $current_folder, click the PDF to see signature. Amazing.
Apologies for those who don't care about my epic terminal journey. I hope this will be the last update ... it probably won't be. Having discovered that `st` doesn't support scrollback, I've decided it's not for me. Apparently the Suckless Tools programmers think you should use a terminal multiplexer (`screen` or `tmux` usually) inside your terminal if you want scrollback. Seriously? That's a lot of overhead, both for memory usage and mental modeling. No thanks. There are also software patches, but again: not interested in building my own if I can avoid it. I've added `foot` to https://www.gilesorr.com/blog/linux-terminal-memory-usage.html . It only runs under Wayland, but fulfills most of my expectations and is surprisingly light on memory. _And_ it supports pixel-perfect images with `timg`, joining the small group of terms that do that. For the near future, it looks like I'll be using `lxterminal` on X11 and `foot` on Wayland. Evan: if Debian packages ghostty, I'd add it to the stats. :-) Although I'll also add that you can do terminal splitting with any terminal using `tmux`. Not saying that's better or worse, but might offer more choice. On Wed, 6 May 2026 at 23:32, Ron via Talk <talk@lists.gtalug.org> wrote:
Giles Orr via Talk wrote on 2026-05-06 19:48:
Here's the whole thing as a blog post, with the Konsole info added.
https://www.gilesorr.com/blog/linux-terminal-memory-usage.html
Thanks.
I had to try this `timg` since it works inside konsole, and "wow" it's really nifty. I had no idea this was possible, but sure is handy. ------------------------------------ Description: GTALUG Talk Unsubscribe via Talk-unsubscribe@lists.gtalug.org Start a new thread: talk@lists.gtalug.org This message archived at https://lists.gtalug.org/archives/list/talk@lists.gtalug.org/message/XVUF4DT...
-- Giles https://www.gilesorr.com/ gilesorr@gmail.com
On Tue, May 12, 2026 at 1:32 PM Giles Orr via Talk <talk@lists.gtalug.org> wrote:
Evan: if Debian packages ghostty, I'd add it to the stats. :-) Although I'll also add that you can do terminal splitting with any terminal using `tmux`. Not saying that's better or worse, but might offer more choice.
Most on the list didn't see the mail to which Giles responded, because my image was too big. I've scaled it down now. I was asking about whether a single instance of ghostty that was split multiple ways would take up as much resource as multiple instances of the terminal each in their own window. The example I used is attached. I note that ghostty is not in the standard CachyOS repos either and needs to be fetched from the AUR. I wondered why that is and then found this clue on the ghostty website: *openSUSE has dropped
<https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/BMZTZ2DCNWXARP5UD7MECR6PCWOTKR5G/#BMZTZ2DCNWXARP5UD7MECR6PCWOTKR5G> Ghostty from its official repositories as it does not allow packages to depend on a specific version of Zig. This is a crucial issue for Ghostty, as nearly all new Zig releases introduce breaking changes, preventing software targeting a previous Zig version to be compiled.*
Hmm. - Evan
Thanks for "foot". CachyOS has it. Foot and Konsole are the only terminals that can show images correctly with "viu". Manpage says something about server/client, and I think it's like "tmux", but each terminal on its own windows. I'm sure there must be option to collapse them into current window, like "screen" or "tmux". I haven't figured out background yet (black screen hurts my eyes). But, my settings so far are: login-shell=yes initial-window-size-chars=100x24 font=Monospace:size=14 Size-wise: $ ll /usr/bin/konsole /usr/bin/foot -rwxr-xr-x 1 root root 499240 Mar 16 08:45 /usr/bin/foot* -rwxr-xr-x 1 root root 55568 May 7 17:46 /usr/bin/konsole* But, the libraries they pull: $ ldd /usr/bin/konsole | wc -l 154 $ ldd /usr/bin/foot | wc -l 23 On 2026-05-12 13:31, Giles Orr via Talk wrote:
I've added `foot` to https://www.gilesorr.com/blog/linux-terminal-memory-usage.html . It only runs under Wayland, but fulfills most of my expectations and is surprisingly light on memory. _And_ it supports pixel-perfect images with `timg`, joining the small group of terms that do that.
On Tue, May 12, 2026 at 1:32 PM Giles Orr via Talk <talk@lists.gtalug.org> wrote:
I've added `foot` to https://www.gilesorr.com/blog/linux-terminal-memory-usage.html . It only runs under Wayland, but fulfills most of my expectations and is surprisingly light on memory. _And_ it supports pixel-perfect images with `timg`, joining the small group of terms that do that.
Since installing I haven't been able to do copy-paste into or out of a `foot` window, which a deal-breaker if that's how it works. Am I missing something?
Evan: if Debian packages ghostty, I'd add it to the stats. :-) Although I'll also add that you can do terminal splitting with any terminal using `tmux`. Not saying that's better or worse, but might offer more choice.
FWIW: When I first installed it, `ghostty` was too new and wasn't in either the CachyOS repository or AUR. Now it's there, along with its terminfo entry. - Evan
Mitchell Hashimoto is an interesting guy (not the best interview: https://www.youtube.com/watch?v=og-CA4n3nXg&t=4s and something he wrote in 2013: https://mitchellh.com/writing/the-new-normal ) ... but... I don't understand why everyone is so excited about ghostty. I admit it's cool, and the image that Evan posted is impressive, and also that I spend most of my time on MacOS, but I don't understand the excitement. I use terminals a lot, but usually it's a terminal window in Zed or emacs. So please enlighten me! Thanks, ../Dave
On Thu, May 14, 2026 at 3:53 PM David Mason <dmason@torontomu.ca> wrote: ... but... I don't understand why everyone is so excited about ghostty. I
admit it's cool, and the image that Evan posted is impressive, and also that I spend most of my time on MacOS, but I don't understand the excitement. I use terminals a lot, but usually it's a terminal window in Zed or emacs.
So please enlighten me!
Not sure if this counts as enlightenment, but here goes. IMO, YMMV, etc. This isn't just about ghostty. It seems to me that there is something of a renaissance (revenge?) of the console terminal -- now highly capable and customizable -- as part of an alternative to modern graphical desktop environments. It manifests in renewed interest in things like ASCII art (ie, fastfetch, htop and their derivatives) and a new generation of Wayland-based apps such as Hyprland (which functionally isn't anything novel) and the Omarchy desktop environment built on top of it (which is). These are complemented by other components such as Nerd Fonts <https://www.nerdfonts.com/#home>, which include more than 10,000 icons and enable text-based tools to offer visual cues previously only available in GUIs, for a fraction of the resource use. Even the onboard graphics capabilities built into in CPUs have enough juice to power this, not to mention older computers. Maybe I'm just late to the game, but in the last year I've been discovering a new generation of console tools that are fairly new (to me), spurred on by this drive to the console that I wouldn't yet call mainstream but is well beyond niche. I started exploring it and described my journey in another GTALUG post back in September. <https://lists.gtalug.org/archives/list/talk@lists.gtalug.org/message/YJFPS4UGUKEIZUFWNPMKEXMTESOJC3HS/> That introduced me to tools such as yazi, fd and fzf, and I continue to learn about new ones such as `timg` this week. The fish shell, growing in popularity despite its breakage of traditional scripting syntax, is also a part of this movement. In this context, ghostty is just one of a wonderfully growing field of terminal emulators, from super lightweight ones such as `foot` to kitchen-sink AI-infused heavyweights such as Wave <https://www.waveterm.dev/>. Who knew this category would attract so much attention in the mid-2020s? Has Wayland really unlocked *this* much potential? Heck, ghostty even comes with its own terminfo entry <https://ghostty.org/docs/help/terminfo> to enable its enhanced functions, and I haven't touched terminfo since my Unix days. I picked ghostty for my own use after reading a bunch of reviews comparing it favourably to similar ones such as Kitty and Alacritty. HTH. -- Evan Leibovitch, Toronto Canada @evanleibovitch / @el56
From: Evan Leibovitch via Talk <talk@lists.gtalug.org>
This isn't just about ghostty. It seems to me that there is something of a renaissance (revenge?) of the console terminal -- now highly capable and customizable -- as part of an alternative to modern graphical desktop environments.
Another example, Brody Roberson: "The Ratty Linux Terminal Is Absolutely Insane" <https://youtu.be/IyYQZG9vQV0?si=M2vBe-MthaSbJWI2> I don't actually see this as actually useful.
CachyOS has "ratty", but it needs real GPU. Built-in graphic of my Haswell cpu (i3-4170) is "incomplete". The default "konsole" is still the best. :-) On 2026-05-15 07:57, D. Hugh Redelmeier via Talk wrote:
Another example, Brody Roberson: "The Ratty Linux Terminal Is Absolutely Insane" <https://youtu.be/IyYQZG9vQV0?si=M2vBe-MthaSbJWI2>
I don't actually see this as actually useful.
On Fri, May 15, 2026 at 11:43 AM William Park via Talk < talk@lists.gtalug.org> wrote:
CachyOS has "ratty", but it needs real GPU. Built-in graphic of my Haswell cpu (i3-4170) is "incomplete".
The default "konsole" is still the best. :-)
Anyone focusing on the productivity value of `ratty` is missing the point. It's a proof of concept, that injecting 3D effects into a terminal are possible, while winking at you that this isn't one bit about making you faster or more productive at the screen. The author and the reviewer both know this and IMO have been clear about this. One thing that I have noticed is that, for some subset of the folks revisiting the console/shell concept of going GUI-free without losing too much of the familiar, being pretty is as important as being efficient. The number of people who have "riced" their setups and posted the results on Reddit is impressive. And my personal manifestation of this new interest in the pretty is exemplified in the ultra-cool (IMO) animated ASCII-art Omarchy screensaver <https://www.youtube.com/watch?v=Gav0MA9bEJk>. - Evan
Giles Orr via Talk said on Tue, 12 May 2026 13:31:26 -0400
Apologies for those who don't care about my epic terminal journey. I hope this will be the last update ... it probably won't be.
Having discovered that `st` doesn't support scrollback, I've decided it's not for me. Apparently the Suckless Tools programmers think you should use a terminal multiplexer (`screen` or `tmux` usually) inside your terminal if you want scrollback. Seriously? That's a lot of overhead, both for memory usage and mental modeling. No thanks. There are also software patches, but again: not interested in building my own if I can avoid it.
Building your own with Suckless Tools applications is a heck of a lot easier than with other applications, and the fact is, if you want to do something as simple as changing the font, it must be changed in the .h file and then recompiled. This is trivially easy, and is pretty much how Suckless Tools programs are intended to be configured. SteveT Steve Litt http://444domains.com
On Sat, 16 May 2026 at 13:45, Steve Litt via Talk <talk@lists.gtalug.org> wrote:
Giles Orr via Talk said on Tue, 12 May 2026 13:31:26 -0400
Apologies for those who don't care about my epic terminal journey. I hope this will be the last update ... it probably won't be.
Having discovered that `st` doesn't support scrollback, I've decided it's not for me. Apparently the Suckless Tools programmers think you should use a terminal multiplexer (`screen` or `tmux` usually) inside your terminal if you want scrollback. Seriously? That's a lot of overhead, both for memory usage and mental modeling. No thanks. There are also software patches, but again: not interested in building my own if I can avoid it.
Building your own with Suckless Tools applications is a heck of a lot easier than with other applications, and the fact is, if you want to do something as simple as changing the font, it must be changed in the .h file and then recompiled. This is trivially easy, and is pretty much how Suckless Tools programs are intended to be configured.
(Apologies to SteveT - this is an over-reaction to your mostly innocent post. It became a trigger for a rant about a personal frustration.) ----- Saying "if you want to reconfigure, just edit the .h and rebuild" creates a massive divide between old school programmer-hacker-users (like you and me and many of the people on this list) and those who want an operating system that "just works." In the age of Microsoft continuously (and possibly deliberately) degrading their OS, I'd like to see Linux as an OS that's welcoming and relatively easy to use. But even if you argue that Suckless Tools are niche, intended for knowledgeable users like us and not newbies (Suckless has made it pretty clear that that's their intention) ... I think it's unwise to make it necessary to recompile to change settings. Configuration files to change minor settings are a GOOD THING that save users' time. Try to imagine if every piece of software you used (including the kernel, LibreOffice, everything) acted like Suckless: "you want to change that setting? You have to recompile." You'd set aside every Sunday for recompiles (and half your disk space for git repositories), and for the three days until you had the time to do the recompiles you'd be dealing with effectively misconfigured software. We'll always have small clusters of people who are in favour of being exclusionist - people who think hard-to-use Linux is good. And that's their right - although I feel like the only reasons they want it that way are A) so they're a member of an exclusive club, and/or B) they get to feel like wizards because their knowledge of Linux is more obvious. But I disagree with the exclusionist attitudes that go with this - for reasons both broad and personal. I want Linux to be welcoming, and I don't want to spend hours of my time recompiling. -- Giles https://www.gilesorr.com/ gilesorr@gmail.com
Giles Orr via Talk wrote on 2026-05-19 14:17:
It became a trigger for a rant about a personal frustration.)
I share this frustration and am happy you chimed in.
In the age of Microsoft continuously (and possibly deliberately) degrading their OS, I'd like to see Linux as an OS that's welcoming and relatively easy to use.
Indeed, could not agree more. There's an undercurrent of "it should be hard to keep the riff-raff out" mentality that's just bonkers. The more users of FLOSS software, the less the stranglehold of proprietary software, the more users switch to FLOSS, ... It's a virtuous cycle.
Configuration files to change minor settings are a GOOD THING that save users' time.
Excellent point and so obvious that it seems "harder is funner" is the goal for some, which is okay but kind of embraces the unflattering Linux nerd memes. It needs to be countered with "It's not that way for most of us".
We'll always have small clusters of people who are in favour of being exclusionist - people who think hard-to-use Linux is good. And that's their right - although I feel like the only reasons they want it that way are A) so they're a member of an exclusive club, and/or B) they get to feel like wizards because their knowledge of Linux is more obvious. But I disagree with the exclusionist attitudes that go with this - for reasons both broad and personal. I want Linux to be welcoming, and I don't want to spend hours of my time recompiling. I can't elaborate further, this hits the nail on the head perfectly.
Ron via Talk said on Wed, 20 May 2026 16:13:45 -0700
There's an undercurrent of "it should be hard to keep the riff-raff out" mentality that's just bonkers.
That is NOT the undercurrent, and it has nothing to do with riff-raff. What it has to do with is the destruction of DIY, via hypercomplexification, to attract people who probably won't use Linux anyway, and if they tried, are unwilling to edit a file or use Google. A great analogy is automobile air-bags. Air bags are dangerous and injure people in 20MPH collisions because the powers that be specified putting in so much explosive as to protect a person not wearing a seat belt. It's the deliberate detriment of responsible folks to accommodate those who don't want to bother at all.
We'll always have small clusters of people who are in favour of being exclusionist
Well, that's one way of putting it. Another way of putting it the wonderful neighborhood analogy. Small clusters of skilled people create a wonderful neighborhood that's an affordable alternative to the strip mall sprawl, word gets out, the neighborhood becomes hip, strip mall big money comes in strip malling the neighborhood at huge rent increases, and the folks who built it become curiosities and are called "elitist", just before they leave for some place less plastic (poser, whatever you want to call it). - people who think hard-to-use Linux is good. You mean like those championing Gnome3? Or modern Gimp? [snip]
I want Linux to be welcoming,
Linux has always been welcoming.
and I don't want to spend hours of my time recompiling.
[slitt@mydesk st-0.9.3]$ cat jj make clean make tic -sx st.info ./st [slitt@mydesk st-0.9.3]$ time ./jj rm -f st st.o x.o st-0.9.3.tar.gz c99 -I/usr/X11R6/include `pkg-config --cflags fontconfig` `pkg-config --cflags freetype2` -DVERSION=\"0.9.3\" -D_XOPEN_SOURCE=600 -O1 -c st.c c99 -I/usr/X11R6/include `pkg-config --cflags fontconfig` `pkg-config --cflags freetype2` -DVERSION=\"0.9.3\" -D_XOPEN_SOURCE=600 -O1 -c x.c c99 -o st st.o x.o -L/usr/X11R6/lib -lm -lrt -lX11 -lutil -lXft `pkg-config --libs fontconfig` `pkg-config --libs freetype2` 7 entries written to /home/slitt/.terminfo could not allocate color 'brightyellow' real 0m0.732s user 0m0.610s sys 0m0.118s [slitt@mydesk st-0.9.3]$ By the way, the "brightyellow" error was my mistake, not st's. Deleting one line fixes it.
I can't elaborate further, this hits the nail on the head perfectly.
Yep. With Suckless Tools 1 second compiles, you're just compiling your life away. No doubt about it. I'd much prefer a 4 deep 4 wide dependency tree with different versions differently timed with massive attack surfaces and numerous entry points for supply chain exploits! By the way, as I said earlier in the thread, I personally write my software using config files. But I'm certainly not going to ignore the robust simplicity advantages of Suckless Tools just because their config is sometimes in a .h file that's easy to change and recompiles in a second. SteveT Steve Litt http://444domains.com
On Thu, May 21, 2026 at 01:21:06AM -0400, Steve Litt via Talk wrote:
Yep. With Suckless Tools 1 second compiles, you're just compiling your life away. No doubt about it. I'd much prefer a 4 deep 4 wide dependency tree with different versions differently timed with massive attack surfaces and numerous entry points for supply chain exploits!
By the way, as I said earlier in the thread, I personally write my software using config files. But I'm certainly not going to ignore the robust simplicity advantages of Suckless Tools just because their config is sometimes in a .h file that's easy to change and recompiles in a second.
I had never heard of these programs before. I think I will refer to them as suck more tools though, because that sounds like absolute shit design. If you need to keep multiple builds around to handle different settings, that makes a mess, and a given binary can't even tell you what the config was that was used to build that particular version. Config files, command line arguments and environment variables are not hard to support and make things much more flexible. Anything is better than compile time configuration. It looks like someone learned about #ifdef and decided they had a hammer and the solution to all problems. -- Len Sorensen
Lennart Sorensen via Talk wrote on 2026-05-21 19:22:
It looks like someone learned about #ifdef and decided they had a hammer and the solution to all problems.
I think the whole thing is by and for leet haxxor wannabe types. Or it's by someone who thought it fun to troll the leet haxxor wannabe types. Arguably there's a learning experience to be had, but in the worst possible way. Just use Gentoo, Slackware, or Arch if compiling software is your thing. And I'm okay with doing things the hard way just for fun.
Steve Litt via Talk wrote on 2026-05-20 22:21:
There's an undercurrent of "it should be hard to keep the riff-raff out" mentality that's just bonkers. That is NOT the undercurrent, and it has nothing to do with riff-raff.
Yet you contradict yourself in the next sentence:
to attract people who probably won't use Linux anyway, and if they tried, are unwilling to edit a file Who says a new user should be required to "edit a file" instead of Alt+Edit > Preferences and make their changes there?
More of that exclusionary gate-keeping - hits both points A & B in Giles' final paragraph.
What it has to do with is the destruction of DIY
DIY is alive and well (maybe thriving) ... among those who wish to learn new things.
hypercomplexification, piggy KDE
Cutsie, derogatory catchphrases do the opposite of shoring up your argument. But good luck on your 2028 run for POTUS, I guess?
A great analogy is automobile air-bags. Air bags are dangerous
Well, that's a whole new level of ridiculous. Collisions are dangerous, airbags reduce the risk. By a lot.
A US study showed that the risk for a serious head injury <https://en.wikipedia.org/wiki/Head_injury> occurring is 5.495% while travelling 40–48 km/h (25–30 mph). The risk is reduced for passengers to 4.435%. *This risk is lowered by 80.5% to 1.073% when using an airbag*. *The risk for passengers is lowered by 82% to 0.797%.*
https://en.wikipedia.org/wiki/Airbag#Injuries_and_fatalities
We'll always have small clusters of people who are in favour of being exclusionist Well, that's one way of putting it. Another way of putting it the wonderful neighborhood analogy.
That analogy fell apart pretty quickly. Some LUGs, for example, are welcoming and have good conversation. Some are an utter waste of time, where cranks run the show. Even in the small cohort of Linux technophiles there are vastly different neighbourhood cultures.
and I don't want to spend hours of my time recompiling. [slitt@mydesk st-0.9.3]$ cat jj make clean make tic -sx st.info
You make an excellent point. It's Giles' point though, which is repeated below (i.e. you ignored how it does not scale well, for one thing):
Try to imagine if every piece of software you used (including the kernel, LibreOffice, everything) acted like Suckless: "you want to change that setting? You have to recompile." You'd set aside every Sunday for recompiles (and half your disk space for git repositories)
Steve Litt via Talk wrote on 2026-05-20 22:21:
attract people who probably won't use Linux anyway, and if they tried, are unwilling to edit a file or use Google.
This thread reminds me of a recent one on another list (which Steve participated in): a guy wanted to buy a laptop, install Mint, and give it to someone with zero Unix experience. His question to the list was, what books should he include: * Sed & AWK? * Vi & Vim? * Emacs? * Korn shell scripting? * ... Plus:
I'm afraid I am going to insist that she learn Vim.
So, turns out the recipient was not nerdy in the slightest. Saw a university semester's reading list, an insistence on learning some inscrutable text editor, and declined the new Linux laptop entirely. What a waste. She could have been a happy Linux user, maybe passing along that info when the topic came up to her knitting group, bowling league, whatever. But now she probably thinks Linux requires a whole lot of work just to do basic stuff. The opportunity for her as a new user is lost forever. Because someone insisted they go full nerd just to check email, Facebook, etc. What a wasted opportunity. This elitist attitude is worse than useless, it's actively detrimental.
Ron via Talk said on Fri, 22 May 2026 02:02:12 -0700
Steve Litt via Talk wrote on 2026-05-20 22:21:
attract people who probably won't use Linux anyway, and if they tried, are unwilling to edit a file or use Google.
This thread reminds me of a recent one on another list (which Steve participated in): a guy wanted to buy a laptop, install Mint, and give it to someone with zero Unix experience.
His question to the list was, what books should he include:
* Sed & AWK? * Vi & Vim? * Emacs? * Korn shell scripting? * ...
Plus:
I'm afraid I am going to insist that she learn Vim.
Just so we're all on the same page, somebody other than me (initials JD) said "I'm afraid I am going to insist that she learn Vim." Given Ron's next paragraph, which I include in the quoted text at the end of my email, makes it ambiguous to me whether Ron realizes this or not. I was the one who suggested postponing learning and use of Vim until the new user was more experienced with Linux, and the "I'm afraid I am going to insist" was a reply to my suggestion.
So, turns out the recipient was not nerdy in the slightest. Saw a university semester's reading list, an insistence on learning some inscrutable text editor, and declined the new Linux laptop entirely.
SteveT Steve Litt http://444domains.com
Steve Litt via Talk wrote on 2026-05-20 22:21:
A great analogy is automobile air-bags. Air bags are dangerous and injure people in 20MPH collisions because the powers that be specified putting in so much explosive as to protect a person not wearing a seat belt. It's the deliberate detriment of responsible folks to accommodate those who don't want to bother at all.
I see your point now:
To provide crash protection for occupants not wearing seat belts, United States airbag designs trigger much more forcefully than airbags designed to the international ECE standards used in most other countries. You're right, they seem to have been overly aggressive to protect idiots not wearing seat belts.
However, wasn't it was dealt with for the most part in the 1990s?
TRW <https://en.wikipedia.org/wiki/TRW_Inc.> produced the first gas-inflated airbag in 1994, with sensors and low inflation-force bags becoming common soon afterward. Dual-depth (also known as dual-stage) airbags appeared on passenger cars in 1998. By 2005, deaths related to airbags had declined, with no adult deaths and two child deaths attributed to airbags that year. However, injuries remain fairly common in collisions with airbag deployment.
I still reject the notion that airbags are a great analogy to some "destruction of DIY" to "attract people who probably won't use Linux anyway, and if they tried, are unwilling to edit a file or use Google". Sounds like your usual anti-systemd rhetoric, which has nothing to do with attracting Windows users, and makes impossible things pretty easy for sysadmins.
participants (8)
-
D. Hugh Redelmeier -
David Mason -
Evan Leibovitch -
Giles Orr -
Lennart Sorensen -
Ron -
Steve Litt -
William Park