3 ms·
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 mas
by cyphar 10y ago
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.
- mistermann 10y agoIn 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.