4 ms·
This looks great, will be working with this in the next few days. I've always had a bad relationship with asdf as it seems to break existing tool management in
by mystickphoenix 4y ago
This looks great, will be working with this in the next few days. I've always had a bad relationship with asdf as it seems to break existing tool management in creative ways that I'm unable to untangle without uninstalling it completely (long story, much thrashing of keyboard and mouse).
- moomoo11 4y agoThe alternative to asdf (at least for me) is to just quit programming. It does what it is supposed to do well enough because in years I have not found anything better or necessary to replace it with.
- e12e 4y ago> ... asdf as it seems to break existing tool management in creative ways Do note that asdf re-uses existing tooling, so trying to combine ruby-build and node version manager and asdf with node and ruby plug-ins is likely to crash and burn (because you end up forcing existing tooling to fight with itself). Not sure if this was what caused your problems - but my asdf-life got a lot more pleasant when just asdf all the things (that I use). Does mean that things like vs code needs the right environment / local tool versions and language servers to work with your projects and vs code plug-ins.