Install Asdf: One Runtime Manager to Rule All Dev Environments • Hacker News Board

Re: Install Asdf: One Runtime Manager to Rule All Dev Environments

#21

Post by matsemann » Sun, Apr 28, 2024, 7:24 AM UTC

jdsalaro wrote: post #17

matsemann wrote: post #9

Because of the insanity of python versions, paths, wheels etc and tiredness of spending time getting poetry install to work for project X due to also needing a full rust and c++ toolchain for some dependency etc.. .. I run everything for a project in a container. Each project then matches perfectly the container actually used in production, so if it works there, it also works on my machine. I just volume mount the pr…

just curious, have you tried using asdf.vm with pipenv ? I've never needed anything else and have yet to have any problems. A couple of moons ago I used Poetry, but gave up on it because it was so heavy and unfortunately would bug out often.

Not tried pipenv, I'm a bit tied by what the company uses.

I did try using something similar to asdf (can't remember the name, think it changed), but it still didn't really solve the problem of OS dependencies and things needing to be compiled, and the problems arising from me not running the same OS as the application would run on. A dockerfile solves that, my system is a carbon copy of the prod environment.

Re: Install Asdf: One Runtime Manager to Rule All Dev Environments

#22

Post by johnathon023 » Sun, Apr 28, 2024, 7:25 AM UTC

jdsalaro wrote: post #13

roylez wrote: post #7

Earlier quoted context omitted.

I still prefer asdf. It does the job just fine. Direnv has its own stdlib, which sometimes I find useful, and make is something I have to install anyway.

I was only vaguely aware of rtx, but after discussing this post at length with people online they've made me aware of the rebranding and the general capabilities of mise. It sure is great, it is! However, like you, I tend to prefer minimalistic and predictable tools. That's why I decided to add the small comment in the discussion section of the post, to be fair but also kind of clear that bloating the runtime manager…

Mise’s #1 objective is to be a really great tool manager, just like ASDF, but way faster and smarter.

However, it turns out that a tool that needs to be extremely CWD-aware also makes a great .env tool and task runner. I was also a little skeptical, but it’s actually super super useful. Especially because it’s easy to convince team members to install it for the tools, they get the rest for free with easy syntax.

Re: Install Asdf: One Runtime Manager to Rule All Dev Environments

#23

Post by johnathon023 » Sun, Apr 28, 2024, 7:26 AM UTC

fredrikaverpil wrote: post #8

I’m liking pkgx over asdf as it can activate project tooling upon cd’ing into a project folder. https://pkgx.sh

Mise gives you basically the same capabilities but is scoped a bit better, I’d check it out.

Re: Install Asdf: One Runtime Manager to Rule All Dev Environments

#24

Post by doctorraags » Sun, Apr 28, 2024, 7:35 AM UTC

Is it just me that never even wants to get to the problems that asdf attempts to solve?

That example in the article of managing multiple python 2.7 versions sounds like a horror story.

Re: Install Asdf: One Runtime Manager to Rule All Dev Environments

#25

Post by jdsalaro » Sun, Apr 28, 2024, 7:38 AM UTC

matsemann wrote: post #21

jdsalaro wrote: post #17

Earlier quoted context omitted.

just curious, have you tried using asdf.vm with pipenv ? I've never needed anything else and have yet to have any problems. A couple of moons ago I used Poetry, but gave up on it because it was so heavy and unfortunately would bug out often.

Not tried pipenv, I'm a bit tied by what the company uses. I did try using something similar to asdf (can't remember the name, think it changed), but it still didn't really solve the problem of OS dependencies and things needing to be compiled, and the problems arising from me not running the same OS as the application would run on. A dockerfile solves that, my system is a carbon copy of the prod environment.

> A dockerfile solves that, my system is a carbon copy of the prod environment.

Yeah, that can definitely not be beat, if at all probably only due to comfort.

> Not tried pipenv

I've been meaning to put a tutorial out there with my workflow since forever, if I had it I'd point you to it.

I recommend you give it a try if you get the chance, you might like it.

Re: Install Asdf: One Runtime Manager to Rule All Dev Environments

#26

Post by jdsalaro » Sun, Apr 28, 2024, 7:40 AM UTC

seivan wrote: post #12

matsemann wrote: post #9

Because of the insanity of python versions, paths, wheels etc and tiredness of spending time getting poetry install to work for project X due to also needing a full rust and c++ toolchain for some dependency etc.. .. I run everything for a project in a container. Each project then matches perfectly the container actually used in production, so if it works there, it also works on my machine. I just volume mount the pr…

Whish there were some CLI to speed up this process actually. Just cd:ing into a folder should pull everything down for you to run iex/irb/node/etc as if it was native but running through the container.

this makes me itchy, pulling the whole internet without looking into your development machine sounds like a very bad idea. It's the equivalent of an IDE's "do you trust this project" but on steroids.

Re: Install Asdf: One Runtime Manager to Rule All Dev Environments

#27

Post by bmitc » Sun, Apr 28, 2024, 7:51 AM UTC

quickslowdown wrote: post #3

thedookmaster wrote: post #2

I've used asdf for years, but recently switched to https://github.com/jdx/mise It's a drop-in replacement for asdf, but I prefer some of the nice features it has to offer. See: https://mise.jdx.dev/dev-tools/comparison-to-asdf.html

I recently started using https://github.com/prefix-dev/pixi for Python projects. I really love it so far, but this tool looks a bit more mature, which makes sense considering pixi is relatively new.

Why this over Poetry?

asdf handles tools, not really packages. So asdf would install Python and not Python packages.

Re: Install Asdf: One Runtime Manager to Rule All Dev Environments

#28

Post by steph-123 » Sun, Apr 28, 2024, 8:01 AM UTC

I like x-cmd because its package system is written in more compatible posix-shell and awk, resulting in much smaller loading and startup overhead. Additionally, x-cmd integrates with asdf and provides AI support, along with over 200 modules for various command enhancements

See:https://x-cmd.com/pkg/

Re: Install Asdf: One Runtime Manager to Rule All Dev Environments

#29

Post by jdsalaro » Sun, Apr 28, 2024, 8:02 AM UTC

bmitc wrote: post #27

quickslowdown wrote: post #3

Earlier quoted context omitted.

I recently started using https://github.com/prefix-dev/pixi for Python projects. I really love it so far, but this tool looks a bit more mature, which makes sense considering pixi is relatively new.

Why this over Poetry? asdf handles tools, not really packages. So asdf would install Python and not Python packages.

My experience with Poetry has been mixed the last couple of times I've tried it, it attempts to do way to many things but often failed to do them properly. Determining dependencies and proper packaging and upload to PyPI are the ones which come to mind.

asdf.vm together with pipenv is my go-to for Python environment management.

Re: Install Asdf: One Runtime Manager to Rule All Dev Environments

#30

Post by pbowyer » Sun, Apr 28, 2024, 8:02 AM UTC

I've had nothing but problems with asdf and nodejs and globally installed tools like yarn reporting "Cannot find node". Perhaps global tools cannot be compatible I don't know; asdf reshim doesn't often fix it.