"I want him to be able to dig deeper. To explore. To try things out, misconfigure, crash, fix, and re-install. To get a feeling for how things work below the surface and how they do not work. To learn how to type fast and efficiently. To create things. Maybe, one day, even to learn how to code if he's interested."

RHEL (and its kin) is a stable server OS. Some organizations that have Linux-based desktops or laptops then also use it on those, perhaps for the sake of homogenisation. But the longer release cycle and conservative update policies that in part make it a stable and predictable server OS also mean that hardware support may lag by years.

This is always a topic on which people will have different experiences. Some people will have everything just working. That's perhaps most likely when the hardware has been chosen with compatibility in mind in the first place. In that case it can be pretty smooth sailing with little tweaking required and with things just working, especially compared to how it used to be, which is probably one reason why people react to claims of endless tweaking being required.

Other people will have hit a rough spot, and those certainly still exist particularly with non-specifically picked hardware, especially if that hardware is newer than the distro release.

CentOS is probably not representative of most people's experiences of running Linux on a desktop or laptop, though.

I will give you that Linux is needlessly complex due to undesirable issues, but that's the price of admission for a highly hackable system, since there are no serious alternatives. As for kids, I wouldn't underestimate them. If what you want to give someone is a rich and deep experience with computers, it's about all you have right now.

On the other hand, and I'm sure this part of my comment will go over swimmingly here, but I imagine... if you start kids out with iPads, what they learn is not that doing interesting things with their computers is challenging, but that it costs a monthly fee.

But I'm not going to let her have one when she's older. I now realise that I would love a Linux tablet. Not a small laptop, but a touch tablet, thin, with a light keyboard too.

Is there such a thing out there? Or should I start building one now?

I pointed out that Linux was the perfect OS for this and your reply was that you hate using Linux on your corporate job because you have to do all those things. I mean fine you can hate it, it's not right for your job, OK. But in addition to being negative, you were off-topic. It spawned a bunch of guys debating the merits of Linux in a corporate office which is not the freaking topic of the blog post and to the extent you want to rattle on about it, you're arguing with a straw man. It shouldn't be a huge surprise you got flak. Sorry if this comes across as elitist but in the context of what this post was about I don't really care that Linux sucks in your office, I did not suggest you should use it there.

What Linux won't do is shove mass shootings and Tiktok ads down his son's throat. Again I quote the post: "What the actual fuck? That kid is 10, and TikTok is one of the things I am actively trying to prevent from getting into his world as long as possible." I maintain: Linux sounds great for this guy and his son.

You ran X11/Xorg (no Wayland), sysv init (no systemd), OSS or ALSA, not pulseaudio, you had sane/not insanely bloated desktops like KDE2 or XFCE.

Even unicode wasn't something most really had to care much about...world was still mostly ascii.

Yes, you had to edit your XF86Config to make your graphics work right, maybe even write your own modeline and be nervous that you screwed up your timings and blew up your CRT permanently. Maybe you had to recompile the kernel to set the proper settings for your Soundblaster. Less fragmentation? Desktop consistency? FORGET IT. A million window managers to choose from. Whichever you go with, your apps will be in a mixture of Motif, Tk, GTK, Qt and/or plain Athena widgets and there are no theme engines that will save you. Just deal with it or write your own.

For those without memory of how it was, search up some screenshots of RedHat 5.2 and its stock FVWM95 window manager. That was the easy to use, business-oriented distro of the day. That was considered acceptable look and feel to ship to an end user.

But all this? Fun. FWIW I still think a kid could have fun tinkering with modern Linux, it's probably just that they would tinker with different things. (Because contrary to popular belief, video and audio almost always "just work" these days)

Rose tinted glasses. Each distro had its own scripts and layout.

SysV sucked.

It was XFree86 -- with separate server binary for each chipset. Then came XFree86 4.0 with a new, hot thing: modularity. You could load drivers as modules, but that presented an entirely new way to make things more complicated. XFree86 became an OS in itself, including dynamic linker, PCI handling, vm86 emulator...

With Wayland, things are much simpler.

> , sysv init (no systemd)

There was bsdinit at the time. Sysvinit was considered bloated by the same types, who cannot consider systemd today.

> you had sane/not insanely bloated desktops like KDE2 or XFCE.

There were other topics, like switching from libc5 to glibc2. Again, unicode, localization, nss services, so much "unnecessary bloat".

Yes, you could map ISO... to ASCII to avoid 'cosas horribles de ver cæmo ⌷stas'. Most words can be read fine without the stress mark in Spanish, except for some verb conjugations where they look odd without them. But, reading n instead of 'ñ' gets tiring after a while.

Thank Plan9's gods for UTF-8.

On the rest, a separate comment it's better.

Also:

I use Hyperbola GNU/Linux. UTF-8. IceWM. Rox if bored, or for photo galleries with thumbnails, here a file manager makes sense. Metal2 theme with CDE icons. I liked the aesthetics from late 90's/early 2000's. I still use

    gv -smartan 

    mplayer2

XFree86 in the early days required you to at least know the refresh rate for your monitor, if not to actually write a modeline which is damn near black magic for most people. This stuff also came with a warning that theoretically you could break your monitor. When you're 12 that stuff is terrifying.

SysV was extremely flaky and system specific. Every distro out there, especially the friendly looking ones like Mandrake bolted on a top of fancy stuff on top that added a whole new layer of complication. Stuff that worked with Debian didn't work on Red Hat.

OSS and ALSA were pure hell unless you had a fancy soundcard with hardware mixing. Dmix required magical incantations to get working, and wasn't reliable because a lot of stuff back then still tried to go through /dev/dsp -- which would break audio for everything else if you had the wrong hardware.

ASCII was probably an okay thing in America, but if you were anywhere else, internationalization was a very un-fun thing to deal with. And if you by chance needed to deal with two non-English languages, that was a constant annoyance.

Bloat is kinda relative. You can still use IceWM if you want to, pretty much every distro has every desktop imaginable.

X11: it sucked. Modelines.

ALSA: DMIX worked, fine.

XFCE: XFCE with XForms and the GPL'ed with GTK was fast as hell. XFFM was delightful to use.

ASCII: Wake up from the coma, please.

America is the whole world? ASCII doesn't even have the £ sign for fucks sake, so it wasn't even adequate for Anglosphere countries, let alone two billion Chinese and Indians.

I also hardly tinkered until I got into programming classes later on the high school, and then it wasn't tinkering, my time spent with Timex, Amiga and MS-DOS was about coding, demoscene and games, not fixing the OS.

I went to the library in '97 and borrowed the Linux Bible, with a CD-ROM copy of Yggdrasil Plug'n'Play Linux that I installed on my 486, and the new world that opened up to me of being able to modify, tune and customize the entire OS to my liking with no restrictions was magic.

Today, I work as a Linux sysadmin and I have fun at work. Other people of the same persuasion are the ones who maintain Linux distributions or contribute to the kernel today.

The point here is that if a kid finds it fun and creative to futz around with "fixing the OS" then let them -- not only is it its own reward, it might lead somewhere. Don't say "no, this isn't fun in my opinion and you shouldn't have to do it".

And in what concerns WebOS, Android and ChromeOS, if it is Linux kernel, BSD, Fuchsia or whatever powering Chrome and Android Runtime, I couldn't care less.