Do you actually have something to add to the discussion? Or you just want to take potshots at me?

You’re all over the place. Please explain why you think using underpowered hardware is the only legitimate way to write software that works on that hardware.

You can write your code on a nice fast machine. A dev machine should be as fast as possible. Those devs with their big fast machines should be required to run and test on much lower spec machines though.

Testing only in a VM on a beefy dev box leads to terribly performing software on customer machines. There's a multitude of performance problems that only come up when a system starts paging to disk, a machine has a HDD, or a CPU gets maxed out. These issues will be completely occulted on a dev machine with tons of RAM, 16 cores, and an NVMe disk.

Far too many developers have the beefy dev box with no requirements to test on more prosaic configurations. Even limiting a VM's CPU and memory isn't a good environment for performance testing because it's still faster than actual low end hardware.

And it can't be cost issue, the crappiest machines are some cheap laptops from any big box retailer. Okay, that fact itself might make getting them harder, but still. Just buy a once a year a low few hundred euro laptop and add to pile. Rotate in 5-10 years or as they fail.

Preach my friend

Yes, I started this discussion thread you're responding to. No, there isn't really a way to do native development without experiencing what your customers do. Build locally on the high powered one, run on your lower spec'd machine. This isn't a potshot. This is me being annoyed that 15 years later, people keep making the same mistakes of not testing on "real world" hardware. Your VM isn't a real user representation. Stop thinking so.

I think the problem is the either or nature. One dev one box is a mistake. The team should have a few they share.

In particular I often fight the slowest machine leaving the office. That should stay for a long time, set aside for testing.