3 ms·
> Node -> npm vendor > Go -> Go Modules These are transparent though. You don't need to "activate" your venv when you enter your project's directory. You can'
by thiht 4y ago
> Node -> npm vendor
> Go -> Go Modules
These are transparent though. You don't need to "activate" your venv when you enter your project's directory. You can't misuse it. You can't fuck up everything because you switched project and forgot to change the venv.
For Go you don't even need gvm or anything like that because of the compatibility promise. Just use the latest and be done with it.
- PaulHoule 4y agoWhen I have been doing analysis work I typically create a suite of command line programs to do that work with. Systems like nom and maven lock me in a prison because they are dependent on the directory I am in…. They take away the ability to cd to an arbitrary directory and run my command line programs. I can’t see why people want to take the X out of Unix like that, maybe they remember using CP/M and never really figured out cd and mkdir and they want to bring us all to their level. With a .venv however the program suite I am running and directory I am are decoupled and I can breathe free.