svu VS eget

View on GitHub

I use svu in a script to get the correct version based on my conventional commit messages (which I write using a tool I made, meteor)

Points that count towards Conventional Commits: - they don't get in the way (as far as my experience with them is concerned) - they enable or leverage tools like caarlos0/svu: Semantic Version Util

Nice tool! Reminds me a bit of https://github.com/caarlos0/svu that relies on prefixes in commit messages for determining the level to increase. The point is that the authors of commit messages usually know best if they only patched something or added a new feature or made a breaking change.

View on GitHub

would be good if you added a comparison with https://github.com/zyedidia/eget on your repo

There used to be a project called ginstall.sh that kept like, a manually maintained database of various projects with static binaries and how to install them. It still exists, but maintenance stopped because its model was also not sustainable. Its use case is better covered by tools like asdf, stew, and if you want to get even simpler, eget.

I'm a huge fan of asdf and have been using for years together with direnv! It's great to see how much effort is put into it! I hope more people adopt it so that we don't have to `curl | sh`! One thing I have issues with asdf is security as are no checksums, so, you if I project get compromised you'll get compromised, too. This, of course, is in addition to the third-party asdf plugin getting itself compromised (which is the greater risk). Last, but not least - I wish asdf came with something like eget [0] incorporated so that it can install 99% of the plugins directly and safely! Last, but not least - 99% of the plugins have almost identical code and all that changes is the repo, so, this should be generalized. For example, many years ago I made just one codebase of all HashiCorp plugins [1] and it's been working great!

[0]: https://github.com/zyedidia/eget

[1]: https://github.com/asdf-community/asdf-hashicorp