g
mise
Our great sponsors
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
g
-
A Journey to Find an Ultimate Development Environment
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).
-
How can I get recent go versions?
I really like g: https://github.com/stefanmaric/g It’s simple, fast to use, and reliable.
-
Managing multiple Go versions in the local environment
If you are using a Unix based system you can use: https://github.com/stefanmaric/g I use it daily and works like charm, I only had some problems using `godoc` but it is solveble if you set the GOPATH to the go location and not the g installation directory
- How can we push homebrew to update go package?
-
Simple But Not Simple For Me lol
Don't use Brew for Go! Brew is great for a lot of things but but not for Go installation. So far this is the best Go version manager i've found. It can be nice to have different versions easily available. https://github.com/stefanmaric/g
-
NVM equivalent in go?
I used this, easy and stable https://github.com/stefanmaric/g
-
setting up Go 1.17.5 on a chromebook
Whatever the language, I find that using a version manager reduces stress considerably. This is the one I use, but there are others: https://github.com/stefanmaric/g
mise
-
Mise is a polyglot tool version manager
Where are you getting "mise uses asdf" from? mise is simply compatible with all asdf plugins. Not the same thing.
It's even said almost at the top of the README.md in the "30 seconds demo" section:
"The following shows using mise to install different versions of node. Note that calling which node gives us a real path to node, not a shim."
https://github.com/jdx/mise?tab=readme-ov-file#30-second-dem...
So yes, mise does not use shims. It only manipulates $PATH. I did benchmarks a while ago and that definitely and consistently has shaved some milliseconds off of the startup times of my tools.
-
Install Asdf: One Runtime Manager to Rule All Dev Environments
mise borrows the plugins from asdf, which also makes it non-cross platform. Interesting discussion on this topic on their GitHub: https://github.com/jdx/mise/discussions/66
Solutions considered include adopting the vfox plugin system or transpiling all asdf plugins to ShellJs.
Now I know that vfox exists.
- Show HN: I made a multiple runtime version manager that can be used on Windows
- Mise-en-place – The front-end to your dev env
- Mise-en-place: The front-end to your dev env
-
Pyenv – lets you easily switch between multiple versions of Python
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.
-
Difftastic, a structural diff tool that understands syntax
direnv + mise does exactly that. When I cd to various directories I get different env vars, it's pretty neat. Setting aliases would just be a case of adding them.
https://github.com/jdx/mise/discussions/1525 for an example of how I use direnv with mise.
https://mise.jdx.dev/direnv.html
https://mise.jdx.dev/templates.html
-
Experimenting with Modern UI Alternatives in Rails
Installed bun js runtime (I used mise, btw)
-
Show HN: Flox 1.0 – Open-source dev env as code with Nix
Not nix based, but I really like https://github.com/jdx/mise too to manage dev tools.
It’s a modern version of https://github.com/asdf-vm/asdf written in Rust.
-
A Journey to Find an Ultimate Development Environment
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).
What are some alternatives?
GVM - Go Version Manager
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
Shadowsocks-Cloak-Installer - A one-key script to setup Cloak plugin with Shadowsocks on your server
pyenv-win - pyenv for Windows. pyenv is a simple python version management tool. It lets you easily switch between multiple versions of Python. It's simple, unobtrusive, and follows the UNIX tradition of single-purpose tools that do one thing well.
gvm - Go Version Manager (gvm) enables seamless installing and swapping between Go versions with a single command. This tool manages a Go environment for the user by allowing a user to specify which Go version they wish to use and handling all of the steps to install and configure that Go version. GVM also supports installing Go from the official Golang master branch so that you can easily try the next version of Go without waiting for a pre release build.
homebrew-tap - Homebrew Tap of HashiCorp products and tools
goenv - :blue_car: Like pyenv and rbenv, but for Go.
Poetry - Python packaging and dependency management made easy
asdf-golang - Go plugin for the asdf version manager
aqua - Declarative CLI Version manager written in Go. Support Lazy Install, Registry, and continuous update with Renovate. CLI version is switched seamlessly
autocomplete - IDE-style autocomplete for your existing terminal & shell
pyenv - Simple Python version management