Why You Shouldn’t Use Vagrant: Real talk from a Vagrant burn-out
Hey, kid. Someday, some charmer is going to smooth talk you.
“Why would you want MySQL and PostgreSQL both running on your machine all the time?” they’ll probably ask. “Just run them when you need them.”
Then they’ll tell you about some slick way their company allowed all of their developers to click buttons on some website, like ordering a Fatty Meal at a McDougle’s: “MySQL, Redis, a custom queue server, and our main app, please.” Then BOOM. They get a fully configured VM, just like that! With exactly the things they need and none of that other crap. They spin it up, they get their work done. No fuss, no hassle. No having developers waste time configuring their environments.
And most of all, your charmer will woo you with how you’ll never again have developers saying, “it works on my machine!” That’ll be their biggest selling point. It will also be their biggest lie.
Don’t you...