Well if we're talking slap dash then sure. But in my use case scenario, you'll only going to be glazing over what should be an environment that will enforce consistency across the team and/or production.

Vagrant (Homestead) is okay, and I'm using it currently at my new job. Didn't stop me already making my own docker environment. It's just more lightweight, consistent, and modular.

No? I was just highlighting what OC said which contained some crucial points. Someone replied who didn't see the problem so I reiterated with the use case in question. So I can only assume you read my comment out of context. Or just didn't agree with OC in the first place.

Of course some will find this useful in other use cases. As someone mentioned they can't run vagrant because their computer wasn't capable. But I still stand by my opinion.

The problem is that Valet is relying on the built in PHP installation as OC said. For a team working on the same project and hosting it this could cause a lot of problems as each dev could have different PHP versions, modules, and configurations. Even with homestead it can still become inconsistent.

I agree using Docker as a solution to keep environments consistent and have a registry repository of the images for PHP, OS, DB, etc. I can't rate Docker highly enough personally.