stable is called stable because of stability
stability
noun [ U ]
uk
/stəˈbɪl.ə.ti/ us
/stəˈbɪl.ə.t̬i/
C1
a situation in which something is not likely to move or change:
a period of political stability
The point of a stable distro is that it’s unchanging. That way you have predictable issues that you can solve in the same way for the lifetime of that version.
Reliability is a side benefit of maintainers choosing the best available version to freeze.
Ackshyually stable only relates to the release schedule. Stability is not reliability.
Plenty wrong with Ubuntu.
But he is the type to ban Russian contributors less than a month after DoD signed a new contract with RH. Can you guess what stocks he owns?
I mean, they almost certainly have built in backdoors like IME. When you can force hardware manufacturers to add shit, you don’t have to think up convoluted solutions like that.
For my wm+Emacs work, I unified the shortcuts by calling a separate go bin that checks if the active window is Emacs or not. If it is, it sends the command to the Emacs Daemon. If it’s not it sends the command to i3. For directional commands like move focus, first check it there’s an Emacs window to that side, if not send the command to i3.
Yeah, who’d hate using a package manager that increasingly slows down your boot time with every package installed, or that uses a closed source store to provide you FOSS
Maybe there’s a reason canonical has to force it on their users
No, Debian doesn’t take your apt install ...
command and install a snap behind your back…
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
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.
Damn you broke my brain for a second there. I thought you meant that nixos replaced k8s, and was wondering what the hell are you talking about.
I was talking about regular fedora. It’s not that you have to reboot, but you don’t get to use those updates until you do. The most obvious example is updating the kernel and its modules.
Linux almost never needs to reboot after an update
Doesn’t it often need a reboot to apply some updates?
I rember reading something along those lines then I was researching why Fedora installs some updates after a reboot. Most
declarative > imperative all day, every day
I’m going to have to come back to Nix/NixOS in a bit.
Use nix + home-manager first for sure. It’s far easier, and you can slowly get into it while making a list of bleeding edge packages.
I’ll probably wait until the official docs catch up as it appears that they are quite a bit behind
Skip them altogether when you’re starting out. I gave up on trying nix the first few times due to how bad they are. zero-to-nix.com is better for learning the basics of nix.
That and I’m not sure how I feel about a DSL for package management. I’d much rather use JSON or YAML, or even INI or TOML.
The closest you can get is home-manager with a list of packages in a json-like format. It’s really not practical to develop a declarative system without a programming language. A basic example would be variables, more advanced would be to write a wrapper that modifies the package so it automatically runs the required cli commands to use your dediated gpu and nixGL with specific packages (nvidia-run-mx nixVulkanNvidia-525.147.05 obs
for example).
It’s sort of like IaC where you’ve got terraform (dsl), pulumi (various languages), and cloudformation (json/yaml). Can you guess which one is universally despised?
Maybe if I were a LISP or Haskell guy.
Then you’d use guix and a dsl made within an actual programming language (much better approach IMO).
That’s such a bad name, I only see lixmaballs.
How do you like it, that’s one of the earlier forks, right?
Should be pointing at the monitor. Xkill only stops showing the process, it doesn’t kill it.