Don’t forget the almighty:

journalctl -fu <servicename>

And yes, I am always reading that as “fuck you, service”.

Company went “here’s your budget for ordering a laptop. Put on it whatever you want”, and so there’s NixOS running on it :)

(To be fair though: small-ish, tech focused company)

Another recmendation for Actual. I spend very little time having to interact with it, because after the initial setup, all transactions are now synched from my bank accounts, and 90% are automatically classified into my categories (not by “AI” or something, you just set rules like “payments to Rewe are always groceries”).

No, not really. The imperativity of ansible vs the declarativity of nix actually does make a big difference in practice.

Grew up on it. My dad set up a Ubuntu 4.10 PC for my brother and I when we were 3/5 (no internet, obv), and it stuck.

Used Windows for a brief time in highschool to be able to play online with friends.

Went right back to Linux when going to university. Will never change back, both for ideological reasons and because Linux is just better.

Next step: NixOS on a phone

Alright, thanks for the info, that’s good to know. Trying to make the jump becomes more enticing every day.

Thanks for sharing! Sounds about as good/bad as I was expecting. How’s the browser experience? Also, are there any features/tweaks you are aware of that you could not get through Nix, that the more “commercial” Linux device manufacturers have developed for their devices?

Holy crap! A NixOS-on-phone user in the wild! You are rocking my dream setup. How’s your experience been with it? Is it remotely daily drivable for phone things?

How exactly does Free, non-open-source software prevent that?

Think about it like this:

• with ansible, you are responsible for making sure that executing the described steps in the described order leads to the desired result

• with nix, you describe what you want your system to look like, and then figuring out how to get there is nix’s problem (or rather, is obvious to nix thanks to nixpkgs)

?

Managing 30+ machines with NixOS in a single unified config, currently sitting at a total of around 17k lines of nix code.

In other words, I have put a lot of time into this. It was a very steep learning curve, but it’s paid for itself multiple times over by now.

For “newcomers”, my observations can be boiled down to this: if you only manage one machine, it’s not worth it. Maaaaaybe give home-manager a try and see if you like it.

Situation is probably different with things like Silverblue (IMO throwing those kinds of distros in with Guix and NixOS is a bit misleading - very different philosophy and user experience), but I can only talk about Nix here.

With Nix, the real benefit comes once you handle multiple machines. Identical or similar configurations get combined or parametrized. Config values set for Host A can be reused and decisions be made automatically based on it in Host B, for example:

• all hosts know my SSH pub keys from first boot, without ever having to configure anything in any of them
• my NAS IP is set once, all hosts requiring NAS access just reuse it implicitly
• creating new proxmox VMs just means adding, on average, 10 lines of nix config (saying: your ID will be this, you will run that service) and a single command, because the heavy lifting and configuring has already been done, once -…

Oh yeah rust tooling is insanely good ootb

I’m too lazy to insert the “look what they need to mimic a fraction of our power” meme here, so… Please imagine it instead.

I’m switching jobs in a couple of months, and I am SO glad to be leaving a (very well maintained!!) python codebase with type hints and mypy for a rust codebase.

It is just not the same.

At this point, package management is the main differentiating factor between distro (families). Personally, I’m vehemently opposed to erasing those differences.

The “just use flatpak!” crowd is kind of correct when we’re talking solely about Linux newcomers, but if you are at all comfortable with light troubleshooting if/when something breaks, each package manager has something unique und useful to offer. Pacman and the AUR a a good example, but personally, you can wring nixpkgs Fron my cold dead hands.

And so you will never get people to agree on one “standard” way of packaging, because doing your own thing is kind of the spirit of open source software.

But even more importantly, this should not matter to developers. It’s not really their job to package the software, for reasons including that it’s just not reasonable to expect them to cater to all package managers. Let distro maintainers take care of that.

Now if Eelco Doolstra wasn’t fucking around, we could have had a super LTS NixOS - but NOOOO.

My exact thoughts lol

Yep, this is the answer. Set it, forget it, accidentally have your hard drive destroyed irrecoverably, and re-set everything up to the exact working state you were used to in under 15min.

It’s a fair bit of initial setup and learning, but afterwards, the word “stable” takes on a new meaning.

Take a look at Kavita for selfhosting bools!

Yeah, +1.

I’ve been an avid fan of applocation launchers like rofi and dmenu on the desktop forever, and the “swipe down and immediately search” feels as close as it can get to the mobile equivalent of those.

Dang, oof