Earlier quoted context omitted.
Can you do those ad-hoc though? I was looking into this too. I feel like it requires a system config change, apply, and then you need to do container start + machinectl login to actually get a shell. That's definitely what I want... most of the time.
Yes, NixOS containers can be run in: * declarative mode, where your guest config is defined within your host config, or * imperative mode, where your guest NixOS config is defined in a separate file. You can choose to reuse config between host and guest config files, of course. It sounds like you want imperative containers. Here's the docs: https://nixos.org/manual/nixos/stable/#sec-imperative-contai...
Why I love NixOS
191–200 of 323 posts
Re: Why I love NixOS
#192I switched over to Nix about a year ago. I was a Windows user before that for 30 years and tried Linux a couple of times, but it never stuck. Now I know I will never touch Windows again. With NixOS I've finally found a system that actually works for me — and the full OS configuration is in a repo. My god, I love it so much. Sometimes I even prefer nix-shells over uv for quick one-off Python scripts. I cannot sufficie…
Re: Why I love NixOS
#193I tried NixOS a few months ago, when I had to choose a new OS for my laptop. On the one hand, it's great, as so many others here and TFA have attested. Declaratively specifying your system configuration and using snapshots to keep track of everything is a complete game-changer. Similarly great is the absolutely huge universe of installable packages. The coverage here is so much better than what's on offer from Ubuntu…
The most NixOS comment I've seen yet was when I was trying to find out about `mkOutOfStoreSymlink`, which lead me to this thread: https://discourse.nixos.org/t/how-to-manage-dotfiles-with-ho... > Hi, I just wanted to know, where can I find the documentation to know more about this contrib.lib.file.mkOutOfStoreSymlink option ? > Well, since is a very simple function, no documentation is really needed. I've been gradua…
It’s a solid os, and I’m enjoying it, and I love that I can’t break things while tweaking. But the docs are and discussion threads are not written for beginners (it’s really hard to write for beginners).
Re: Why I love NixOS
#194Earlier quoted context omitted.
As a NixOS user for 3 years, and a Claude user for 1+ year, I agree with you that it's an ideal fit. I've been very happy with, for example, how Claude can configure GNOME via dconf settings: tweaking those settings declaratively requires cross-domain knowledge and knowing where to dig. But Claude just knows. But trying to set up an environment for one of those perpetually running AIs, and asking it to refactor its o…
also the AI hallucinating nix options. I have to constantly check https://search.nixos.org/packages?channel=unstable
Re: Why I love NixOS
#195Earlier quoted context omitted.
guix would like a word
Does guix have a flake equivalent yet?
https://guix.gnu.org/manual/1.5.0/en/html_node/Inferiors.htm...
Re: Why I love NixOS
#196Earlier quoted context omitted.
Here is a simple workflow with mutable systems like Fedora that I think a lot of people are missing. AI could be brought into this workflow also for those who want that: (1) Take a snapshot of your current system (snapper+btrfs on Linux, bectl on FreeBSD+ZFS) (2) Make destructive changes like install a new windows manager, some drivers etc. (3) If everything worked out well, continue (4) If something failed badly, re…
It’s like saying you don’t need a version control system for coding, as you can just make a copy of your sources before making important changes.
There is no distinction between package maintainers and end users. They have the same power.
In the meantime i dont expect Debian users to ever write a package themselves or to modify one.
In nixOS you do it all the time
Re: Why I love NixOS
#197Earlier quoted context omitted.
I don't agree at all. Just look at these derivations: https://codeberg.org/guix/guix/src/branch/master/gnu/package... I counted and you regularly see this: "))))))))))" at the end. This is not a language that is optimizing for being written by humans.
> This is not a language that is optimizing for being written by humans I've taken a look at the code - having never written a line of Guix in my life - and it seems very readable to me. It's cleanly structured and makes good use of indentation. The string "))))))))))", which you claim you're seeing 'regularly', appears exactly twice in 4,580 lines of code. It's the longest parens string that appears in the file. See…
And yes your example is better, but still terrible. The point is not the formatting. The point is that there is that 10 deep nested code is just not easy to understand. I would also say a line of c/python that does 10 nested function calls as unreadable. But they do not encourage this, whereas with lisp its modus operandi to write such incantation.
Re: Why I love NixOS
#198Earlier quoted context omitted.
It reads almost the exact same as any functional C-style language. Not to mention that specifically for Guix, you're going to be writing the (name value) form for 99% of it.
I don't agree at all. Just look at these derivations: https://codeberg.org/guix/guix/src/branch/master/gnu/package... I counted and you regularly see this: "))))))))))" at the end. This is not a language that is optimizing for being written by humans.
Re: Why I love NixOS
#199Earlier quoted context omitted.
Pasting the generally horrible error messages is also quite effective!
Pasting? Give Claude/codex the ability to go fix it itself and have it deal with it directly.
Re: Why I love NixOS
#200"Loving" any OS is strange to me. It's just a tool. I don't love my kitchen knife, or car. Nor do I love my computer, or any application on it. Web3, Rust, NixOS. The holy trinity of cult-like appreciation. I do wonder what brings forth such fanaticism.