open-conference-url VS asdf

I like Alfred but I'm not a huge power user. It does have a bunch of other functionality. Out of the box it lets you do a bunch of stuff like filesystem manipulation, clipboard history management, a simple calculator, and stuff like that.

It's also extensible. For example there's a very useful add-on workflow [0] that makes it really quick to open up the next Zoom meeting you have scheduled in your calendar.

[0] https://github.com/caleb531/open-conference-url

here some ex of workflows that I use - Low Power mode helper - https://www.alfredforum.com/topic/17707-low-power-mode-—-toggle-low-power-mode-for-battery-or-power-adapter/ - Character count workflow - https://github.com/ibnuh/alfred-character-counter-workflow - https://github.com/RyanVerhey/character-counter-alfred-workflow - https://github.com/crispgm/alfred-strlen - Cron helper - https://github.com/crispgm/alfred-cron - Browser tabs navigation - https://github.com/epilande/alfred-browser-tabs - Colors - https://www.packal.org/workflow/colors - Ts converter - https://github.com/snooze92/alfred-epoch-converter - Find2kill process helper - https://github.com/xeric/alfred-find2kill - Private tab helper - https://github.com/vinaywadhwa/Go-Incognito-Private---Alfred - Chrome history helper - https://github.com/manifestinteractive/alfred-workflows/tree/master/Chrome%20History - Hide/see hiden macos files helper - https://www.alfredforum.com/topic/4168-toggle-hidden-files-workflow/ - MacOS host helper - https://github.com/iOvergaard/alfred-hostsfilemanager - Http status code helper - https://github.com/ilstar/http_status_code - Lorem ipsum generator - https://github.com/raarellano/alfred-lorem-ipsum-workflow - Open conf call helper - https://github.com/caleb531/open-conference-url - Password generator - https://github.com/epilande/alfred-password-generator - Pretty JSON - https://www.packal.org/workflow/pretty-json - Quick folder navigation (I use for download folder) - https://github.com/vitorgalvao/alfred-workflows/tree/master/RecentlyAdded - Quick finder <-> terminal helper - https://github.com/LeEnno/alfred-terminalfinder

I use this workflow made by Caleb - https://github.com/caleb531/open-conference-url

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

Or if you need to manage more than just node, asdf has been around for over a decade and works great. You can use a .tool-versions to change runtimes for each project you have, in addition to managing your global runtime versions

https://asdf-vm.com/

Why not just use a tool like asdf (https://asdf-vm.com/) or mise (https://mise.jdx.dev/)?

These tools have the advantage of not being multi-taskers and can manage version for all your tools. You wouldn’t need pyenv and npm and rvm and…

We’ve even started committing the .mise.toml files for projects to our repos. That way, since we work on multiple projects that may need multiple versions of the same tool, it’s handled and documented.

The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise).

(asdf)[https://asdf-vm.com/] fully supports Python and almost any other language. I've been using it for Ruby, Python, Elixir, and other languages for years and never looked back.

Secondly, our development environments must not drift, because then code may behave differently and a change could pass on our machine but fail in production. There are many tools for locking down environments, e.g nix, pkgx, asdf, containers, etc., and they all share the common goal of being able to lock down dependencies for an environment accurately and deterministically. And that needs to be enforced in our local workflow so we don't have to rely on CI environments for correctness. All developers must have environments that are effectively identical to what runs in CI (which itself should be representative of the production environment).

There are many ways this can be done (e.g nix, pkgx, asdf, containers, etc.), and we won’t get into which specific tools to use, because we'll instead cover the essential essence of preventing environment drift:

I've really been enjoying asdf, which is a program that allows you to install specified versions of dev utilities as well as dynamically manage them via shims and .tool-versions files.