> I don't see how replacing the "it works on my machine" with "it works in this VM" is much better. It is the same problem. I can run a VM on both my machine a

> I don't see how replacing the "it works on my machine" with "it works in this VM" is much better. It is the same problem. I can run a VM on both my machine and yours. > You just added the overhead of running another whole computer in your computer to solve it. A VM hasn't had the overhead of running a full computer in a long time. Depending on your platform, containers (or hyper-V) are near-native performance. And let's be real, when your dev environment is spending 45 minutes running eslint, a 1-2% overhead isn't going to make or break you. > Also the author states he is locked into using VS Code, which seems like a risky dependency to have. Lockin isn't a binary bad thing. Flexibility isn't free. Supporting every possible workflow in every possible environment ends up with catering lowest common denominator, which sucks. If VSCode dies, I'll move onto a replacement, just like I did when we (thankfully) decided eclipse was to go to the farm.