4 ms·
This is exacerbated by the fact that most developers have nice, beefy machines compared to most people who will be using their products. Though we've also expe
by tempestn 3y ago
This is exacerbated by the fact that most developers have nice, beefy machines compared to most people who will be using their products. Though we've also experienced the opposite in the case of server-side code. Improved a lot of little inefficiencies in our server-side code base through efforts to keep it possible to run on small VMs on developers' local machines. Things that we'd never notice on the monstrous 52-core 128GB of RAM infinity SSD servers, but show up quickly when you're giving it 2 cores and 4GB in a VM.
- cure 3y agoThere is a school of thought that developers should have hardware that is a generation behind the cutting edge, to make sure that their output will perform really well in the real world, on the latest hardware...
- xp84 3y agoCan't do it in the modern day with any front-end "technology" -- I remember finding after converting a FE build to Docker that it would die every time with a strange error. Turns out the Docker VM couldn't (maybe still can't?) make use of virtual memory on the dev machine, and there weren't 10GB of real RAM to spare. Let that sink in for a moment how building a frontend web app takes 10GB of RAM. (No this wasn't my code, or choice of dependencies). I hate the js ecosystem.