Having everything in a single file is not really a problem.
Having extremely outdated info on topics like below is a major issue though.
One cannot have bookmarks, or refer to page numbers.
Shareni
joined 1 year ago
Icy peepee
Or
I see peepeee
???
I mean, org-mode was invented because LaTeX is too hard
73 and 76, but I got them mixed up, ed is older.
That's for original Emacs though, the gnu version came out in 85
Emacs is older than ed
Sure, and not every arch user ends their comments with btw.
But that was consistent across multiple years, devices, and derivatives. It's usually a 5 min fix/workaround, but it's still annoying.
Inb4 it becomes/is a subsidiary of the NSO group....
Nobody's raving about the install, that's just useful for people who don't know what makes a Linux distro.
It becomes your personality after a few years because every update might break anything, and you need to regularly maintain random shit. Also if you forget to update regularly, the chance of everything crapping out rises exponentially.
I hope you're using something like btrfs, because rollbacks are a must.
Second council of Nicaea?
Does your company have a serious IT department that manage devices?
If yes, then you'll need to do whatever they say, and be ready to be told that's not happening.
If not, I'd suggest a stable distro, encrypt the disk, and use flatpak/nix to install fresh packages. Fedora could work, but I've had bad luck with it, and wouldn't want to risk my device crapping out because of an update.
The rest is really going to depend on your work and your it department.
Separate your system and user lists. Use home-manager for example for your user packages. I think separating those configs is the official recommendation.
As for the rest, I'm using nix on MX because of declarative package management. Screw going back to imperative and having to remember what packages to install. If it's something I use often it goes on a list, if I don't nix shell comes to the rescue.
I'd rather mess around with dev envs for nix than distrobox.
Xkill doesn't kill the process, it just stops showing it to you