Probably this: https://マリウス.com/a-word-on-omarchy/#summary

I have not opened my SMS app in years.

But that actually is an asshole move then. Because a lot of emotional attachment and memories can be in a chat.

It is absolutely NOT fine from a technical perspective

Prisoner Of War:

The one exception here: it’s great to have it installed on your parents’ PC when you’re the one doing the update once in a while when you are around. Rock solid in between, no nagging, and if something did break, easy to roll back.

Because a commit should be an “indivisible” unit, in the sense that “should this be a separate commit?” equates to “would I ever want to revert just these changes?”.

IDK about your commit histories, but if I’d leave everything in there, there’d be a ton of fixup commits just fixing spelling, satisfying the linter,…

Also, changes requested by reviewers: those fixups almost always belong to the same commit, it makes no sense for them to be separate.

And finally, I guess you do technically give up some granularity, but you gain an immense amount of readability of your commit history.

Same. And even if you were to fuck up, have people never heard of the reflog…?

Every job I’ve worked at it’s been the expectation to regularly rebase your feature branch on main, to squash your commits (and then force push, obv), and for most projects to do rebase-merges of PRs rather than creating merge commits. Even the, uh, less gifted developers never had an issue with this.

I think people just hear the meme about git being hard somewhere and then use that as an excuse to never learn.

Out of curiosity, where on this curve lies “20k lines of Nix config”? (Asking for a friend 👀)

Drop if-let

Over my cold dead body. if-let-else is such a fantastic pattern. Makes everything an order of magnitude more readable. Works so nicely for unwrapping opts/errs.

I’m just going to leave this here: Wigner’s friend.

In Timelike Infinity, there’s a group following that logic through to its conclusion, committing a bit of terrorism on the galactic scale to make Ultimate Observer-senpai notice them from the end of time and the universe.

Batshit insane, 10/10, one of Baxter’s tamer plotlines.

No problem. If you do decide to give NixOS a try, feel free to ask about anything should things be unclear :)

Yeah… I heard that too, about half a year after I got really into nix.

To be honest, I try to keep away from community drama as much as possible, so I am not entirely up to date here. I think (and I might be wrong, if someone reading this knows better, correct me!) there’s three main points of contention:

• Queer, PoC, and other “minority” users experienced harassment on (semi-)official channels (Github, Discord, Forums): That fucking sucks. I’m queer myself and lucky enough to not have experienced any of that in my time with Nix, but if I had not decided on Nix yet and learned about this before getting invested, it might have given me enough pause to not put any time into this. In all honesty however, that’s sadly a problem with many, many OSS projects.
• Governance and Funding: I do not know much about the governance, afaik there was a bit of drama about the inventor of Nix acting like a (benevolent?) dictator for life, but those issues should have been resolved with a new governance model. The really big, inciting incident of a lot of community drama with Nix through was a bit over a year ago, when the committee in question decided to let Anduril fund a NixCon, against the explicit and loud protests of the community. That sucked. Hard. While obviously all kind of shit companies use all sorts of great OSS projects, inviting Anduril to sponsor your official conference is… not really understandable.
• Conflicts of Interest: the aforementioned inventor of Nix owns a company heavily invested in the nix ecosystem. A bit reminiscent of the way that, say, Google holds Chromium by the balls, though to a much less severe extent. Miraculously, features that are “extremely unstable” in nix (but wanted by the community for a long time) suddenly get released in closed source to enterprise customers… However, the open source project is separate from, and not beholden to the whims of, said company.

My position on all three points is this: They are not great; but a) they do not threaten the ecosystem, which is mature and independent of this drama, and not reliant on one or a couple of central, potentially problematic, people; and b) there are community projects that actively and effectively do distance themselves from all of these points (namely: Lix) and which are drop-in replacements for the core nix language and compiler, meaning if the upstream project actively did something to really piss you of, you could move with very little work to something independent of Nix.

I hope this will not become necessary, because Nix is genuinely magic. Once you get the hang of it, nothing on your computer is particularly difficult anymore. You also get the best-in-class package management (and it’s easy! Once you have configured your own system to your liking, you already know everything you need to package your own software and contribute to nixpkgs!), being “bleeding edge” yet at the same time incredibly stable (seriously, I have switched all of my servers and VMs to Nix and I have not had one single incident once, including after updating machines after forgetting about them for 1.5+ years).

Anyways. Sorry for the wall of text lol.

As someone else has said: NixOS. You said in a comment that you use Arch because of the AUR. Good news, nixpkgs is larger and fresher than the AUR, without needing to tap into any kind of third-party/unofficial repo.

The unstable branch is essentially a rolling release (and very stable despite its name). I am happily gaming on it with Steam. During installation, you can just choose to not install a desktop. (However, due to how nix works, it’s trivial to rip out the entire DE at any point, should you so choose.)

But it is a learning curve for sure. Steep, but not very long.

Was gonna say. Nix matches all of OPs boxes.

• if your skill is so great that you would never cause the kinds of bugs the rust compiler is designed to prevent, then it will never keep you from compiling, and therefore your complaint is unnecessary and you can happily use rust
• if you do encounter these error messages, then you are apparently not skilled enough to not use rust, and should use rust

In summary: use rust.

Last place of employment had develop as the default branch. Actually quite liked it. (There also was a main branch, which only got merged into as part of the release flow, so might as well have called it release, I suppose.

Anyway, IMO it communicated “volatile and subject to change” a lot more clearly than things like “head of main” etc

You misunderstand! It has also turned into basically a hobby (and recently, a job, lol) to manage nix configs.

Those 19k lines are clean, well-structured and DRY, and do describe every little thing about ca. 30 machines.

maniacally laughs while trying to avoid eye contact with 19k lines of nix config

KDE, GNOME and Sway are the only functional Desktop Environments/Window Managers that support Wayland all, while the Other DEs are not even close to shipping with Wayland.

What