Custom kernel (Accessory, rare):

• Must be crafted by the owner and cannot be sold, given away, or otherwise transferred. Sometimes explodes during the crafting process, causing unconsciousness and 2d6 damage.
• 10% attack and defense bonuses to weapons and armour that were equipped at the time of crafting, but -10% on new weapons and armour.
• Lightness grants +10 speed.

Thing is, even when Ubuntu’s software has been packaged outside Ubuntu, it’s so far failed to gain traction. Upstart and Unity were available from a Gentoo overlay at one point, but never achieved enough popularity for anyone to try to move them to the main tree. I seem to recall that Unity required a cartload of core system patches that were never upstreamed by Ubuntu to be able to work, which may have been a contributing factor. It’s possible that Ubuntu doesn’t want its homegrown software ported, which would make its contribution to diversity less than useful.

I’d add irrational hate against Canonical to the list of possible causes.

Canonical’s done a few things that make it quite rational to hate them, though. I seem to remember an attempt to shoehorn advertising into Ubuntu, à la Microsoft—it was a while ago and they walked it back quickly, but it didn’t make them popular.

(Also, I’m aware of the history of systemd, and Poettering is partly responsible for the hatred still focused on the software in some quarters. I won’t speak to his ability as a programmer or the quality of the resulting software, but he is terrible at communication.)

And you have fixed versions every half a year with a set of packages that is guaranteed to work together. On top of that, there’s an upgrade path to the next version - no reinstall needed.

I’ve been upgrading one of my Gentoo systems continuously since 2008 with no reinstalls required—that’s the beauty of a rolling-release distro. And I’ve never had problems with packages not working together when installing normally from the main repository (shooting myself in the foot in creative ways while rolling my own packages or upgrades doesn’t count). Basic consistency of installed software should be a minimum requirement for any distro. I’m always amazed when some mainstream distro seems unable to handle dependencies in a sensible manner.

I have nothing against Ubuntu—just not my cup of tea for my own use—and I don’t think it’s a bad distro to recommend to newcomers (I certainly wouldn’t recommend Gentoo!) Doesn’t mean that it’s the best, or problem-free, or that its homegrown software is necessarily useful.

On the one hand, diversity is usually a good thing for its own sake, because it reduces the number of single points of failure in the system.

On the gripping hand, none of Ubuntu’s many projects has ever become a long-term, distro-agnostic alternative to whatever it was supposed to replace, suggesting either low quality or insufficient effort.

I’m . . . kind of torn. Not that I’m ever likely to switch from Gentoo to Ubuntu, so I guess it’s a moot point.

My experience (which is admittedly many years out-of-date) is that WINE isn’t very good at anything except games, because games are what the people who use it and work on it are most interested in. When other software works, it tends to be as much by coincidence as anything.

Switch to a distro lineage whose package manager builds in the necessary facilities? Someone’s already mentioned Nix, and Gentoo has the --fetchonly switch for Portage which will download (but not install) everything required for a specified package including dependencies, so you can copy all of the files to an external drive at once.

You just said “large”. I would consider any project with 10MB or more of source “large”. Firefox is certainly large by that standard, but so is openssl. If your standard for “large” is “has at least as much code as Firefox”, then according to you, the Linux kernel is a small project.

openssl is a vital part of the web, but it is a small tool

You consider 61.7MB of source code “small”? (That’s for openssl 3.3.2, and may not include some rust code that isn’t in the gzipped main code package.) I think maybe you need to recalibrate a bit.

A whole bunch of non-user-facing projects providing vital libraries that are largely ignored until something blows up in people’s faces, as happened with openssl some years ago. Some of them contain quite a bit of code (for example, ffmpeg, which underpins a lot of open-source media playback software). Among browsers specifically, Pale Moon has been around for years, is maintaining a lot of code no longer carried by Firefox along with a fair amount of original code, and has no cash source beyond user donations, which might stretch to paying for the servers in a good month.

The projects with corporate sponsorship, or even a steady flow of large donations, are in the minority. There’s a reason the xkcd about the “project some random person in Nebraska has been thanklessly maintaining since 2003” exists.

Money isn’t important. Some complex software is, in fact, maintained by unpaid volunteers who feel strongly about the project. That doesn’t mean it’s easy (in fact it’s quite difficult to keep the lights on and the code up-to-date), but it is A Thing That Happens despite being difficult.

What is important is the size of the codebase (in the case of a fork, that’s the code either written for the fork or code that the fork preserves and maintains that isn’t in the original anymore), the length of time it’s been actively worked on, and the bus factor. Some would-be browser forks are indeed trivial and ephemeral one-man shows. Others have years of active commit history, carry tens or even hundreds of thousands of lines of novel or preserved code, and have many people working on them.

It can share TDE’s popcorn.

If you’re interested in doing the tech equivalent of a party trick (except that it’s less interesting to watch), go ahead and try. You’ll probably just end up reinstalling almost every package on the system that differs between the base distro and the offshoot. Harmless, but also pointless, since you could just have installed Debian from the get-go and saved yourself a lot of trouble.

There are a whole bunch of Very Silly Things you can do in the Linux world that aren’t worth the effort unless your income relies on the creation of niche Youtube vids. For instance, it should theoretically be possible to convert a system from Debian to Gentoo without wiping and reinstalling. I’m not going to try it.

My primary icon theme and widget style are 20+ years old and not flat in the least. You can still have that look and feel on a real computer if you want it (but you may have to compromise elsewhere or do some extra work). On phones, all bets are off.

Dunno what your issue with that icon pack is, but I’d bet there’s a good chance it can be solved with a few file renames or symlinks if you care enough to bother.

Most people are not obsessed monomaniacs with room for only one interest in their lives. That means that most Linux users are interested in things other than free software, so many will choose to “dress up” their computers in ways that showcase their other interests, and may use material that is not under copyleft licenses to do so. If this causes you anxiety or confusion, you may want to speak to a mental health professional. Seriously.

I ended up setting up custom themes for multiple different widget sets to get a true black background. It was easy for most QT variants, not too bad for GTK2, really awful for GTK3 because it doesn’t have proper documentation for manual theme creation, and I haven’t tried to tackle GTK4 yet.

Because they all need different configs (and the window manager title bar etc. may need yet another one), it’s difficult to give suggestions unless you tell us which terminal and window manager software you’re trying to theme—the requirements for a Gnome session are different from those for something like fluxbox. Some terminal software even has its own built-in theming support.

TDE. Functional, stays out of my way, but still reasonably full-featured. The development team is dedicated to adding useful features while keeping the original look and feel, so I don’t have to go hunting for settings that have inexplicably moved or changed defaults every time I update. It doesn’t support Wayland, but I’m Wayland-neutral (that is, I have nothing against it, but I have nothing against X either).

Yet another, “well, yeah, technically it has security ramifications, but I’m not admin’ing any multiuser machines, so I’m not losing any sleep over it” bug.

Gentoo supports either configuration, as it does with a lot of things. My systems were installed with split /usr and I have no intention of changing that, because the merge adds no value for me.

Um, if your primary use is typing accented letters, why don’t you just set a compose key? The character sequences you need to type are much more intuitive, and you don’t get this type of problem.

In my case, I have scroll lock (the most useless key on the keyboard) set as a compose key. To get “é”, I type scroll lock, then e, then '.

You can set a compose key using setxkbmap, for instance setxkbmap -option compose:sclk. (If scroll lock isn’t to your liking, there are a number of other modifier keys that can be used instead—list here, starting around line 810.) You can also specify it permanently using X configuration files, although I don’t know the exact method.

The GPU doesn’t care about the CPU, or vice-versa. AMD is probably better value for money right now if you’re intending to replace both CPU and mobo, but Intel will work.

The reason you don’t see AMD CPU + nVidia GPU in premade machines these days has to do with corporate contracts, not interoperability. Before AMD bought out ATI, it wasn’t an uncommon combination.

Even if the original issue had anything to do with ISOs, he’s way overestimating the level of protection on many install ISOs, in my experience—they’re just disk images, and presumably all the files read off them are passing through Ventoy itself. Even if you find one that performs some kind of verification, easy enough to change a jump instruction to a no-op somewhere in the machine code guts of a file as it passes through Ventoy, and prevent the verification from executing. (The difficult part is figuring out which instruction to change, but people have done it before.)