

Sorry, but the person above made a blanket statement that Jellyfin sucks for music streaming.
Alas, it does not; example: me, guffaw
Sorry, but the person above made a blanket statement that Jellyfin sucks for music streaming.
Alas, it does not; example: me, guffaw
Have zero problems with Jellyfin as the Server, Symfonium as the client on mobile / music assistant for streaming to sonos at home
Out of curiosity, where on this curve lies “20k lines of Nix config”? (Asking for a friend 👀)
How exactly does Free, non-open-source software prevent that?
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.
Github, Lemmy, my blog.
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:
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.
I just started working at a new place, and my closest coworker has my deadname. Threw me for like half a second, but hasn’t been an issue at all otherwise.
Using a docker container provides you with the exact amount of extra protection as using a VM: zilch.
Only advantage is you can use other people’s config easily.
Haha, perfect 😄
Would you mind opening a PR to fix that typo? Would be useful for others as well!
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
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)
I honestly don’t get the hostility, wtf.
If you prefer something other than Jellyfin, good for you.