4 ms·
I've tried to think why this is, and I think it is because no one wants to make things faster because that would be admitting you didn't do it right the first t
by o_m 6y ago
I've tried to think why this is, and I think it is because no one wants to make things faster because that would be admitting you didn't do it right the first time. So product owners try to hide it under the rug, and they'll focus on things they can present to their own leaders so they are on good terms all the way.
- hutzlibu 6y agoI rather think most devs have overpowered hardware for developing - and simply don't notice performance drops directly on consumer hardware.
- reassembled 6y agoMy friend develops PixelCNC, an OpenGL app for generating 3D tool paths from 2D images, on a netbook because he knows many of his users have under-powered older systems.
- iKevinShah 6y agoThis is so true. My workstation was i5 2nd generation with my development code running on a partition which was on HDD, the timings for every request were ~200ms to 1s depending on multiple factors. Page performance in chrome was constantly ~1s total. I upgraded to latest i5 with SSD for data, and the performance drops are basically 0. It bothers me that there is something which needs improvement and I cant check on a commit to commit basis. But yes, it is very easy to oversee performance drops due to new / faster hardware.