3 ms·
I see comments about Nix and I've heard rumblings about it before, so I might look into that. But Docker covers my needs for version management completely. To
by trey-jones 5y ago
I see comments about Nix and I've heard rumblings about it before, so I might look into that. But Docker covers my needs for version management completely. To me it seems much more explicit, more portable, less error prone, less complex than any of these virtual environment managers. Never mind that I don't even want node.js on my system if I can help it at all (I can't, generally).
- hushpuppy 5y agoDocker doesn't allow for LSP servers in my text editor. Asdf "just works".
- trey-jones 5y agoThis is a reasonable point, and something that is being worked on. I definitely think Docker can provide LSP servers as necessary, we're just not quite there. This is something that I'm interested in working on, though I'm not the only one: https://github.com/emacs-lsp/lsp-docker https://github.com/emacs-lsp/lsp-docker For the most part, latest version linting is good enough for me, currently.
- dlisboa 5y agoIt's obviously doable, but it's very heavy for languages. Like someone else said, you immediately run into basic issues like readline, LSP compatibility, volume persistence, port forwarding, etc. Docker is better for version managing services like databases, caches (Postgres, Redis, etc), things that have little need for different configuration or exploration and persist through multiple sessions. Once they're up, they're done. Asdf is the next best thing for local development, where you need that kind of exploration.
- rkangel 5y agoThe main issue with docker is that you have to start from scratch with your environment. With Nix you can layer it over your existing Linux environment (or you can have it from-scratch by running `nix-shell --pure`). There are advantages to the docker approach, and Nix can be painful to get going, but a significant portion of the community (including me) find the pain to be worth it.