For run of the mill sys admin stuff, you don’t need to dive too deep. Even my reasonably complex needs of containers and mixed workstations is, imo pretty parsable from an intuitive perspective. I was reluctant at first but once I saw how a general sys admin would use it, it made my life so much easier.

Highly recommended.

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.

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

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

nearly impossible with FDM

I’m not in the space, but what’s your opinion of acetone vapor treatments to get a bit higher polish for fdm?

Isn’t he Jewish?

The nix wiki, packages an options pages are all I need most of the time.

Sounds like IPFS or torrents.

BAR is so good!

Seriously. WTH did people expect?

A classic.

Shots of olive oil?

Custom ROMs are limited due to closed nature. Make sure whatever you want to load on it explicitly supports the chip before you buy, of that’s your thing.

Nothing a few Rc<Box<RefCell>>s can’t fix!

Do it! The initial work is probably larger, but the payoff is a hugely stable system.

NixOs everywhere except my phone. It takes about 2 hours to go from blank drive to 100% identical device when a drive fails. Can’t beat it.