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

Chrome tabs each have their own process though, so then wouldn't your problem be your PC?


Sure. But if three instances of a website can bring a fairly new machine to its knees, then there's nothing any browser could reasonably do to fix Twitter's massive JS bloat.


In my case, FF uses well less than 10% of CPU, yet the browser is extremely unresponsive. So no, it's not the machine, it is FF.




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

Search: