I guess that’s true, tbh the reproducibility aspect is really what I like about nix, and I guess I’m confusing a bit here. I guess I’m saying nix gives a good compromise with immutable generations and high repro, but you’ve convinced me it’s not immutable per-se.

If you control everything in the build it is, and every generation is immutable.

At the surface, you can pin the commit you pull packages from, but if you want to go deeper, you can essentially define your own channel and dependent binaries, allowing you to store every aspect of how a generation is built.

It can be made to be by pinning various things which are not by default.

Htop had some good lights, but btop is better

Nah you gotta submit a bug report for that

Finally, a meme for my high precision, low accuracy quadrant.

March to the sea.

Only cause of that darn brain implant.

They ran arch, btw 🥲

H̸̨͇̣̯̥̫̄̕e̴͍̮̯͗̓̐̓̚ > i

Like this? https://m.youtube.com/watch?v=GYLBjScgb7o&pp=ygULZnVyYnkgb3JnYW4%3D

It’s full of stars

That’s cute

Weird way to spell NixOS but ok

I like htop more, but btop has better colors and graphs (imo)

Is this… surprising behavior on Nintendo’s part?

Indeed. This is what I use, and it effectively supplants the need to have an local vm manager.

Then you can add remote builds, nas connections, and you basically have a “server less” app server. In the past when there is a hardware failure on the workhorse, getting back up is a script invokation and a reboot away - data is persisted on a nas.

If you enjoyed that you should check out https://www.levenez.com/unix/

At&t did this precise thing to us.