I think about it like this:

Layer 2b: ->> User applications (flatpak, nixpkgs, etc.)

Layer 2a: ->> User data (mutable, persistent no matter what your system layer is)

Layer 1: -> System (immutable/read-only/updated "atomically" meaning all at once) 

Layer 0: Hardware

Or, alternately, it’s what macos has been doing with absolutely no fanfare for several versions now. That’s not a knock, btw. It’s an illustration that it can be completely transparent in use, though it may require some habit changes on linux.

I cannot for the life of me figure out what is going on (but I’m not terribly involved). I can tease out that he was disruptive, but I cannot figure out in what manner he was so.

Still, this feels like a Grade-A old school Internet community meltdown from the early 90s.

11 months later …

NixOS looks interesting whoosh sucked into a warp

And that’s without counting the roll-your-own variants. uBlue has been a remarkable project.

Upvoting not because you agreed with me but because of the relief of discovering my flagrantly innocuous frustration might have a kernel of justification.

Let’s see.

Bearnaise Bechamel Apple Pesto Ketchup Sweet BBQ Chimichurri Gravy Panang Romesco Tabasco Mustard BBQ Vinegar BBQ Mustard Mole Garum

The scale admittedly ramps up exponentially at the end there.

It appears that it is. The first version, February-based, is 24.2. The next scheduled version is 24.8, scheduled for release in August.

If that’s the case, I’m less saucy, but my understanding was that the numbers were based on the release month. (Noting for emphasis that I cannot overstate the absolutely minimal nature of my irritation and that it doesn’t detract even a whisker from my appreciation of Libreoffice! It’s almost, but not quite, tongue in cheek.)

I’m still saucy (in magnitude, bechamel not mole) that the version numbering is yy.n (24.2) and not yy.nn (24.02). The actual versioning combines the “was there a version .1?” problem with a sorting issue if there’s both 24.2 and 24.10.

Obsidian, logseq, and others work natively with markdown files that are almost cross-compatible and can be edited and used in any text editor. Things like back linking may not be present in that case (of using a plain text editor) but it doesn’t disappear from the file.

Roam uses a proprietary format but exports to markdown.

That’s pretty much how I got where I am. Started with Fedora, then Silverblue, then Ublue, then fleek (a custom front end for Home Manager), then, when I saw what Home Manager and Nix could do, dove into NixOS fully.

First, I don’t disagree with that, but I’m always conflicted. Like, eza is better than ls. Atuin is magic history search. btop/fish/helix etc. etc. etc. But for just getting started I almost want to discourage finding alternative tools. But I also don’t lol.

Also, I am 99.9% certain this exchange is how most distros get started. “We can do a more sensible set of defaults!”

Day 1: Sway looks cool Day 11: SwayFX looks cooler Day 29: Hyprland looks wild Day 44: niri looks fun Day 63: This WM I found on a repo by a random Serbian guy looks great. Day 97: I WROTE MY OWN WAYLAND COMPOSITOR AND WINDOW MANAGEMENT CONCEPT FROM SCRATCH

I look back on learning to live with NixOS and laugh. It made my brain hurt, and if I’d only found the Misterio77 repo sooner, it would’ve saved a lot of premature aging. But, if you have some basic familiarity with programming concepts, it’s an easy OS to live with, just different. And so, so, so, so powerful.

They do desperately need a set of opinionated example builds and much better documentation.

One of the more annoying things about living in Florida is that we have closely related animals that are nearly identical, but they don’t have glow-butts. (At least not down in the bottom half of the state.)

I’ll wait for someone from like Lakeland to say they have them.

Pretty sure the motivation here is more along the lines of “double tap so they don’t get up.”

Given the “unlearn what you have learned” problems I’ve encountered on my own Nix journey, I wouldn’t be surprised if that happened with shocking rapidity. Nix isn’t really THAT hard. It’s just (a) different and (b) obscurely documented.

My kid, believe it or not, uses a NixOS laptop regularly. He doesn’t configure it yet, but honestly I’m not afraid of him having a go. When I was just about his age, I was figuring out DOS without the Internet to help, and while it was orders of a magnitude simpler, the documentation was orders of a magnitude more sparse too. Any of the big, well-documented distros (Ubuntu, Debian, NixOS (for some values of well-documented anyway), Fedora) would be fine. Honestly, I’d even let him loose with Arch at this point, or even Linux From Scratch.

Birds. Servers are big, strong, imposing birds. Mobile devices are small and flitting birds. Things in between are birds in between. I’ve put some thematic value on some of the bird names (a showy bird for media, etc.).

I had a thinkpad that got much of the way there. I never tried ZFS encryption, but I’m sure someone in the nixos world has figured that out.