PHPEnv VS HomeBrew

If you don’t want to use docker, I’d suggest looking at PHP Brew or phpenv

Note that it won’t be practical for all cases. If you really want to run native services and multiple environments just use Homebrew to install stuff and an env manager like phpenv.

I advise you to learn about docker, but yes, there is a tool like nvm, that is https://github.com/phpenv/phpenv

I've not tried it, but https://github.com/phpenv/phpenv might be what you need. I use the Java, Groovy, Python and node versions of this, and they work extremely well.

https://github.com/phpenv/phpenv does the job for me

I use phpenv personally, but using the official PPAs at https://deb.sury.org/ is the most maintainable. phpenv lets you set a PHP version per folder, globally, or even temporarily. I am constantly switching between PHP versions during the day and it was easier than messing around with update-alternatives (contrast with Java, where I use update-alternatives because the version switching is much less day-to-day for me)

If you don't have Homebrew installed, grab it from brew.sh first.

Installation (using Homebrew): If you don't have Homebrew installed, you can get it from https://brew.sh.

Since you're on macOS, Homebrew is your friend for installing and managing software like PostgreSQL. If you don't have Homebrew installed yet, head to brew.sh and follow the installation instructions.

Homebrew is the go to for developer using MacOs to be able to install applications. It's the equivalent of Aptitude in Ubuntu.

Install Vagrant using Homebrew:

Thanks for the kind words <3

Rewrite in Rust: never :)

A non-Ruby frontend may be possible but, fundamentally, the Formula DSL is Ruby and we couldn't feasibly move to another language without breaking backwards compatibility with everything.

The "update tons of stuff you never asked for": we're working on this: https://github.com/Homebrew/brew/issues/19202

Performance in general: we're doing what we can to improve it wherever possible. Ruby makes this harder but it is getting better rather than worse at this point.

> I wonder if you can get away with not doing parallel downloads, but just keep the sequential downloads going in the background while it is installing a package?

I could be wrong, but I believe multiple people, including maintainers, have looked into exactly that :-)

(I also need to correct myself: there is some work ongoing into concurrent downloads[1]. That work hasn't hit `brew install` yet, where I imagine the question of concurrent traffic volume will become more pressing.)

[1]: https://github.com/Homebrew/brew/issues/18278