The main issue most people have with asdf is that it’s annoyingly slow. Not unusably so, but just enough that it’s irritating.

I identified [0] the source for much of it (sub-shells and pipes) and began a PR [1], but became bogged down with BATS testing, and then found mise / rtx, so kind of lost interest. Sorry. You can always implement these if you’d like.

[0]: https://github.com/asdf-vm/asdf/issues/290#issuecomment-1383...

[1]: https://github.com/asdf-vm/asdf/pull/1441

> Just as one starts getting popular ...

asdf hasn't just started getting popular. It's been popular for a long time already. IIRC I started using it ~8 years ago (~2016). asdf has been around since 2014. I believe Mise (rtx) has been around for a couple of years already too.

Fair. Honestly, I hadn't heard of it until about a year ago, up until then I was using pyenv and rbenv independently.

Same here. Never heard of it until a few months ago when I got back into Ruby on Rails after 12 years.

Also, contrary to the other comments in this chain I don't find it particularly slow..

I mean you can apply this argument to just about anything, it isn’t really unique to “this industry” or computing in general.

People will generally change taste and likes/dislikes every few years.

You don’t have to stop using asdf if you like it.

It's normal to build new stuff based on the experience we got from what came before. If you like asdf, use asdf, there's nothing wrong with using it, and there's nothing wrong with wanting something "better" (depending on what "better" means for the user)