3 ms·
I was highlighting the difference in ease of use. While you can do anything in nix and provide versions you want, it's not as nicely wrapped as asdf. For some t
by viraptor 4y ago
I was highlighting the difference in ease of use. While you can do anything in nix and provide versions you want, it's not as nicely wrapped as asdf. For some things supported by asdf, like elasticsearch, nix requires a lot more work. It's a bit like the old dropbox-via-rsync comment - it's true you can do these things through shell.nix, but that's not why people use asdf. There's space for a flake wrapper which will make things much easier.
- MichaelGlass 4y agoYeah I wish you could just start with a `.tools-version` and nix would generate a development flake. Someday! That being said, the task of debugging a deprecated tool version in asdf just one time makes the investment in the nix awkwardness worth it. the pitch for nix isn't that it's a nicer tool than, e.g. `asdf`, but rather, that it will probably work in five years. frightful flashbacks of of trying to get nokogiri to build.
- Cloudef 4y agoSome people are doing these kind of wrappers, for example: https://github.com/luispedro/nixml https://github.com/luispedro/nixml Machine learning people usually use anaconda which is all sorts of mess... But honestly yeah, I think it's worthwhile to invest learning nix for simply guaranteeing your environment still works for years to come and isn't affected by side-effects (some thing outside of your environment description actually is causing the whole thing to work, or some thing outside the environment is making the thing not work).
- floxdev 4y agowe're working on something like this :) Check out https://floxdev.com https://floxdev.com
- viraptor 4y agoSlightly off topic, but that page lags like crazy on ff mobile. I was trying to read/scroll it and it wasn't a great experience.