nyan

Actually, I don't think you could break a system in quite this way in Gentoo these days. Portage generally doesn't remove packages during upgrades (certainly not unrelated ones that would break the depgraph!). It would have exited with (in this case) a message about version conflicts before changing any packages and left it for the user to sort out. Modern versions of portage do a pretty good job of keeping you from shooting yourself in the foot by accident, while leaving you with a lot of leeway for doing so on purpose.

Assume anything you can buy has a shelf life and set a yearly reminder on your calendar to copy forward stuff more than five or so years old, if those files are of significant value to you. Or for the documents, print them out—paper has better longevity than any consumer-available electronic storage.

That being said, quality optical discs are probably the best option in terms of price to longevity ratio for the average person right now. Just keep in mind that they are not guaranteed to last forever and do need to be recopied from time to time.

(I have yet to have a DVD fail on me, but I keep them in hard plastic jewel cases in climate-controlled conditions, and I've probably just been lucky.)

I prefer Claws Mail. It does what I need it to.

It was a legitimate but extremely rare concern with some early printers, yes (Wikipedia points out a particular early laser model from Xerox, plus an experimental machine from 1959, as printers that have legit caught on fire, but also points out that there is no known report of one of the old industrial-sized line or drum printers ever catching fire from friction despite it being a hypothesized failure mode). Thing is, those printers were, I believe, all obsolete by the time the Linux kernel was written. So the "on fire" error message is not likely to have been congruent with reality for any machine actually running Linux.

We're talking about a kernel whose user-visible error messages have historically included things like "lp0 on fire" . . .

There's an old joke from a couple of decades ago about what operating systems would be like if they were airlines:

Linux Airlines

Disgruntled employees of all the other OS airlines decide to start their own airline. They build the planes, ticket counters, and pave the runways themselves. They charge a small fee to cover the cost of printing the ticket, but you can also download and print the ticket yourself. When you board the plane, you are given a seat, four bolts, a wrench and a copy of the seat-HOWTO.html. Once settled, the fully adjustable seat is very comfortable, the plane leaves and arrives on time without a single problem, the in-flight meal is wonderful. You try to tell customers of the other airlines about the great trip, but all they can say is, “You had to do what with the seat?”

Gentoo is still very much a "You had to do what with the seat?" distro, while most others have retired that concept to varying degrees, at the cost of the seats being less easy to perform unusual adjustments on.

Assuming that it works out, yes, this might fix the problem. On the other hand, I remember gcj, which kind of quietly vanished after a while, so I prefer to reserve judgement until gcc's Rust implementation is ready for production use.

You say that as though it's a bad thing. 😆

One detail about Rust in the kernel that often gets overlooked: the Linux kernel supports arches to which Rust has never been ported. Most of these are marginal (hppa, alpha, m68k—itanium was also on this list), but there are people out there who still use them and may be concerned about their future. As long as Rust remains in device drivers only this isn't a major issue, but if it penetrates further into the kernel, these arches will have to be desupported.

(Gentoo has a special profile "feature" called "wd40" for these arches, which is how I was aware of their lack of Rust support. It's interesting to look at the number and types of packages it masks. Lotta python there, and it looks like gnome is effectively a no-go.)

Large organizations always have politics—it's human nature. 1700 people is quite a large organization. Therefore, the kernel maintainers have politics. The presence of politics always means that some people will get stomped on unfairly.

This is all business as usual, in other words, and it will not go away. At best, you can shift the culture of the group and the politics along with it, but that takes time and effort and people-handling.

For files? An unholy amalgam of snake, kebab and dot, depending on what exactly I'm trying to convey. (I still have much-ported files around with DOS 8.3 filenames, so they're truncated scream case (SCREAMIN.NAM), but I don't actively name files like that anymore.) The important thing is to separate the words/sections while using characters that are valid without escapes in both ext4 and vfat if at all possible.

For variable names, camel or Pascal case (depending on language convention) if I think anyone else is going to read it. Flat case for code I don't think anyone else is ever going to see (don't do this—it has left teethmarks in my ass from time to time and will do the same to you).

Some individual window managers are full-featured enough to be somewhat usable as program launchers all by their lonesome, such as awesome, fluxbox, and openbox. There's also Enlightenment, which is somewhere between a bare WM and a DE. If you really want to play with standalone WMs, start with something from this paragraph.

Other WMs need a bunch of other things like dmenu and feh piled on top of them to get a useful environment. i3 is one of these. You can find and fit together enough software pieces to get a fairly full-featured environment out of one of these setups, but it's more work than just installing the core portions of a DE.

Figure out first whether you're dealing with X or wayland (hyprland is a wayland compositor, which is slightly different from a window manager). Read guides, and especiallly stay away from things that say they're "lightweight" or "minimalist" until you've read the documentation and know exactly what you're getting into, as they tend to be for advanced users. If you just want to play around and have no particular problem you're trying to solve, just look for live CD/DVD/USB images you can boot inside a VM and save yourself some work.