Linus has already chimed in, and wants Zstd to just use the standard way of checking for CPU features instead of rolling their own. Apparently, that would be even faster, compiling to a single jump instruction.

Very likely. Or, at least what the thread commenter meant. There’s other programs vulnerable to …/, but it’s mostly some kind of Application Firewall, one that inspects the message itself.

They can, yes. You’ll need an experienced psychologist to diagnose that, probably. At least it’s not me, too insecure to answer honestly, instead thinking about the “socially correct” answer, because mine would be either too telling or a cringe reference.

All hail the third temple OS!

Mutter is made by GNOME, what do you expect?

snix (rest in piss)

Nix Lix Guix

Client-side decorations. In most DEs and WMs, the compositor or the shell is responsible for the window border, Close button etc. On GNOME, the client (application) is expected to do all of that. There is a mechanism for a WM to request an app whether to draw CSD, and for the app to request SSD, but they don’t need to be implemented.

Then the deal needs to be changed. Contracts are not above the law 🤷

The nixos-unstable channel actually does ensure a minimum set of required packages work: Those that would prevent you from booting. The compiling-from-source is because Hydra (the binary cache) only starts building once a package appears in nixpkgs-unstable, and if it immediately proceeds into nixos-unstable, or one of its dependencies is different there, that build won’t be finished yet. release- and versioned nixos- don’t have that problem, as they have a merge freeze, and are mostly fast-forwarded along unstable.

What would be good is a mechanism for Hydra to tell you “I tried to build this derivation, and it failed.” For this, Nix first needs to store build failure, and since store paths are input-addressed by default, you can also skip builds that will certainly still fail.

Btrbk if you use the right filesystem.

I used to use an old consumer Yoga, and now a new ThinkPad. Some say it’s the wrong way around, I say I want more than 2 cores and 8GiB of RAM. (Un-)Fortunately, I got hooked on the Nix and Tiling-WM drugs quite soon, and so there wasn’t a lot of distrohopping.

Not Linux, and of course the perfect OS.

You should try it, to get a taste of what is possible, then learn what to do, and maybe even stay. But it’s not for beginners, the terminal-phobic, or people that rarely use their PC.

It doesn’t need fiddling, but it invites you to do so. And the default setup is hardly a best practice: swap on a partition, no FDE, no zram… missing FDE in particular will require you to reinstall, and you better have found out how to do proper backups including metadata.

Arch

There are valid use cases for JS and AJAX, but they are few. HTML/CSS is great, and has gotten many new features that can replace JavaScript in the long run: Popovers, commandfor etc. One thing I am missing is opening arbitrary popovers on a long hover. For that, you still need mousemove event listeners.

nix flake update --commit-lock-file && nh os switch

Distros are a matter of taste, and you shouldn‘t judge someone over it. But a bit of friendly fun-poking is alright (e.g. „NixOS user spend all night configuring their PC“). Insults directed directly at a person are never OK. And there are of course distros that are objectively bad (like Ubuntu), and you can criticize their creators, and maybe try to convince the users to choose something else (that‘s where Mint is from, kind of), but you cannot. hate. on. them.