4 ms·

I'm happy my team switched off asdf, it's not ready for prime time. It has baffling bugs, like selecting the wrong version of installed tools. It introduces asd

I'm happy my team switched off asdf, it's not ready for prime time. It has baffling bugs, like selecting the wrong version of installed tools. It introduces asdf specific problems that you have to debug to use it for daily activities. I do not recommend it.

amrox 4y ago
That does not sound like my experience. Are there GitHub issues for the bugs you mention?
- stevebmark 4y ago
  Yes, there are more than 100 open issues, which unfortunately I don't think the author has enough bandwidth to triage. Bugs keep piling up. https://github.com/asdf-vm/asdf/issues https://github.com/asdf-vm/asdf/issues
  - amrox 4y ago
    It’s all relative but 100 open issues doesn’t sound bad for a somewhat popular project to me. For example, rust-lang/rust has over 8000. Regardless, I curious if there were _specific_ issues you had. And following that, I’m also curious what you moved to instead.
trebbble 4y ago
Sounds a lot like our teams' experience with yarn a few years back when every post was like "yarn is a perfect replacement for npm, npm is now deprecated, LOL don't use it or you're an obsolete fool". It became a running joke that any project attempting to start with yarn (we had lots of JS devs, so of course they all try the new shiny) was only going to make a it a couple weeks before they hit some baffling, misleading, hard-to-diagnose error that was entirely solved by running "npm install". Tons of npm features missing in yarn, tons of sanity checks that npm did that yarn simply omitted. Maybe it's gotten better but it's made me even more skeptical of "common wisdom" around these things. (To be fair, it may be better now, but this was well in to the time when folks were starting to sneer at people still using npm and running around saying how much better yarn was and how there was no reason not to use it—I can only assume these folks weren't doing much with it, because it was really easy to hit those kinds of problems.)
quaunaut 4y ago
What solution did you switch do?

amrox 4y ago

That does not sound like my experience. Are there GitHub issues for the bugs you mention?

stevebmark 4y ago
Yes, there are more than 100 open issues, which unfortunately I don't think the author has enough bandwidth to triage. Bugs keep piling up. https://github.com/asdf-vm/asdf/issues https://github.com/asdf-vm/asdf/issues
- amrox 4y ago
  It’s all relative but 100 open issues doesn’t sound bad for a somewhat popular project to me. For example, rust-lang/rust has over 8000. Regardless, I curious if there were _specific_ issues you had. And following that, I’m also curious what you moved to instead.

trebbble 4y ago

Sounds a lot like our teams' experience with yarn a few years back when every post was like "yarn is a perfect replacement for npm, npm is now deprecated, LOL don't use it or you're an obsolete fool". It became a running joke that any project attempting to start with yarn (we had lots of JS devs, so of course they all try the new shiny) was only going to make a it a couple weeks before they hit some baffling, misleading, hard-to-diagnose error that was entirely solved by running "npm install". Tons of npm features missing in yarn, tons of sanity checks that npm did that yarn simply omitted. Maybe it's gotten better but it's made me even more skeptical of "common wisdom" around these things. (To be fair, it may be better now, but this was well in to the time when folks were starting to sneer at people still using npm and running around saying how much better yarn was and how there was no reason not to use it—I can only assume these folks weren't doing much with it, because it was really easy to hit those kinds of problems.)

quaunaut 4y ago

What solution did you switch do?