Like many of you, I work on a lot of different projects. Even when a project
is less serious—hey, I should check out this new JS framework!—I
strive to reduce the friction involved with setting up the project's dev
environment to the absolute bare minimum possible.
This sounds really good if you need packages or something like that set up, but honestly, most people will be perfectly fine with asdf. It doesn’t need to start an environment or load anything. It just makes the shims for your tools active for the current directory, and it doesn’t require .env files, it doesn’t require dealing with package managers. It simply is a file where each line is the name of the tool and the version. That’s it. And it just works. Every time. Unless it’s Python. Fucking Python.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
Follow the programming.dev instance rules
Keep content related to programming in some way
If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos
This sounds really good if you need packages or something like that set up, but honestly, most people will be perfectly fine with asdf. It doesn’t need to start an environment or load anything. It just makes the shims for your tools active for the current directory, and it doesn’t require .env files, it doesn’t require dealing with package managers. It simply is a file where each line is the name of the tool and the version. That’s it. And it just works. Every time. Unless it’s Python. Fucking Python.