I have never personally used asdf, but working as DevOps I had to help many fellow Devs untangle their environments because they messed up with asdf and everything broke down. One time someone installed it on a build server to try to manage python binaries and all builds stopped working.
Maybe if I got some time to explore the tool I would have a better appreciation for it, but from my experience it is too easy to mess things up.
asdf is not a good DevOps tool, you shouldn't use it on production, you can use it but is not really it's focus. What it excels is being a consistent development tool, for managing many stacks (node, java, ruby) versions for different environments
Whatever tool I use to get Python onto a system I never call it directly except when running python -m venv <name> to set up the environment my code will run from.
> untangle their environments because they messed up with asdf and everything broke down
I remember the bad old days when all that version management was typically done just right on your machine, often with different versions of python/ruby/etc installed globally with sudo.
Docker can be a pain and can be slow and it's arguably a worse-is-better solution, but it's so much less painful for consistently managing versions.
Maybe if I got some time to explore the tool I would have a better appreciation for it, but from my experience it is too easy to mess things up.