Earlier quoted context omitted.
> Need to work inside a container because it's 2025 and we don't need to clutter our local machine with 100s of dependencies and env managers... “Can I tell you about our lord and saviour Nix?” Kidding, but seriously though I’ve found having to work in a container to be a bit clumsy, even with good tooling around it. As you said it’s 2025, and there are other ways to have reproducible toolchains that don’t pollute th…
> “Can I tell you about our lord and saviour Nix?” The "just use Nix" people are just like the "write it in Rust" brigade. And the things both groups promote share exactly the same problem ... A stupidly enormous learning curve. That's why your average person prefers to just the job done in a container vs Nix, or in Go vs Rust. I'm sure Nix is awesome, just like I'm sure Rust is awesome. But honestly, I've got enough…
Zed is our office
341–343 of 343 posts
I think LLMs have solved that for Nix. I recently moved my homelab from an Ansible/Debian setup to NixOS. As long as I understand at a high level what Nix is and what problems it solves, I can let the LLM deal with the configuration language.
Re: Zed is our office
#342Re: Zed is our office
#343Earlier quoted context omitted.
I didn’t say “just use Nix”, I jokingly made a reference to street evangelists and the similarities they have in their approach with people who are excited about a particular technology. In fact I said “Nix or otherwise” implying there are many options when it comes to reproducible per-project environments.
joking or not, people are very tired of the evangelists (fanbois?) from these ecosystems, and this culture around them is one reason others stay away. The broader trend is developers are burnt out on tooling churn
(That’s the joke)