Notch’s Bugatti is far less likely to spontaneously combust (because it was made by professionals, not AI), and if it did, it wouldn’t affect as many people. Omarchy claims to be an easy version of Arch, when in reality, it’s just doing what every beginner would be doing, including all of the accidental security holes, and then adds some more weakpoints through the unchecked shell scripts.

Part of those 8 million do go into paying “the Hyprland guy” (Vaxry)'s salary, and he himself hasn’t been very politically correct. DHH also is quite open about choosing “anti-woke” projects (i.e. without a CoC).

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.

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.

Mutter is made by GNOME, what do you expect?

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.

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

Technoblade never dies! Tom Scott came back, so I was right staying.

How does Mastodon‘s „Open URL“ work then? It works with the URLs I get from Lemmy, so it does support some other software…

1. Create your own Codeberg repo for your configuration
2. Use Neovim, maybe with Nixvim

How do I do that with the SSD cache? Everyone just talks about it, but I can’t find any documentation…

I have them at home and as such don‘t need to spend money on them.

Follow up question: Do I need a separate CPU cooler, or is the boxed Wraith enough? And how loud is it? I can’t really find info on that.

The NAS drives are here because they are from an old NAS which only uses a cheap dual-core Intel, has 2G of RAM, and boots from eMMC. So anything would be an upgrade…

Nix is absolutely not just for CI, the idea is to use it locally as well, so the CI runs in the same environment.