Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My experience with the contemporary mobile web leads me to believe that 90% (100% of mass-market sites) of front-end coders are doing their work on quad-core CPUs and calling it a day.


I can't contradict your claim (since I don't work on mass-market sites), but I test my work on a VM with 1 CPU and 1GB ram; if the site doesn't run well in that, it's not good enough. I wish more people tested their software that way. I often find myself performing optimizations that are generally best-practices under V8 (and also work well in Firefox) that most in this community would consider "premature optimizations," at least until you point out that the difference between the two are 20-50x, and something that once cost 40ms now costs under 1ms, meaning your UI is just that much more responsive. For some reason, "it works, I'm done" seems to be a pervasive mental model. How unfortunate.


My phone has a 600MHz CPU and major sites regularly take minutes to finish loading. I've even thought of starting a name-and-shame YouTube channel with videos of this state of affairs with different sites.


I often find myself performing optimizations that are generally best-practices under V8 (and also work well in Firefox) that most in this community would consider "premature optimizations," ...

Do you have any references you could point to? I'm really curious as to whether or not I'm doing something stupidly inefficient. :)





Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: