Your make my point exactly there by following dogma without first assessing the real situation.
Why does it matter that everybody is running the same thing locally? Who cares if somebody is on windows, somebody is on linux?
If the code committed to version control is accurate and the machines can run the code, then there's no issues and there's no need for over-engineering with virtualisation.
As per my original message, it's not "needed" unless you have complexities in your project which means your host machine cannot run it adequately.
It matters because some people will run into problems that others aren't. It solves a very real problem that I've encountered far too many times in my career.
What you're suggesting that due to incompatibilities between your team that you decided to use it to solve that issue.
That's my point - You used it to solve a specific issue on your team.
That is NOT justification for using it for everything "just because" - as most of the time there won't be a need, for example I've been developing a mixture of LAMP/JAM projects for around 20 years - never "needed" it - Yes there's times we could have used it. But never "needed" it.
This is the important information, the difference between "needing it" and "using it".
Your make my point exactly there by following dogma without first assessing the real situation.
Why does it matter that everybody is running the same thing locally? Who cares if somebody is on windows, somebody is on linux?
If the code committed to version control is accurate and the machines can run the code, then there's no issues and there's no need for over-engineering with virtualisation.
As per my original message, it's not "needed" unless you have complexities in your project which means your host machine cannot run it adequately.
It matters because some people will run into problems that others aren't. It solves a very real problem that I've encountered far too many times in my career.
What you're suggesting that due to incompatibilities between your team that you decided to use it to solve that issue.
That's my point - You used it to solve a specific issue on your team.
That is NOT justification for using it for everything "just because" - as most of the time there won't be a need, for example I've been developing a mixture of LAMP/JAM projects for around 20 years - never "needed" it - Yes there's times we could have used it. But never "needed" it.
This is the important information, the difference between "needing it" and "using it".
My experience with this is very different from yours. Lets just leave it as that.