3 ms·
aw man... what OS are you on? Chrome is the CPU and memory hog on macOS... Though I guess Firefox isn't that far behind.
by dwighttk 8y ago
aw man... what OS are you on? Chrome is the CPU and memory hog on macOS... Though I guess Firefox isn't that far behind.
- mschuster91 8y agoSame as you - macOS. I regularly have ~250-300 tabs open on my MBP (though I admit, I cheat via using The Great Suspender), the only time it hogs CPU is when some nasty advertising on sueddeutsche.de or Facebook decide they need to warm my lap. In addition, I vastly prefer Chrome's devtools. Nothing comes close, and I believe this is a huge part of why developers are so Chrome-loyal.
- dwighttk 8y agohuh. I guess Ghostery isn't protecting me enough. My computer gets angry when I have just a couple of Chrome tabs open. Though I haven't tried it for general browsing in a long time.
- atomwaffel 8y ago> In addition, I vastly prefer Chrome's devtools. Nothing comes close, and I believe this is a huge part of why developers are so Chrome-loyal. So do I (I’ve also heard good things about Firefox’s dev tools but never made the switch), which is why I use Chrome for web development and Safari for everyday browsing. It works really well for me and I like that my browsing history isn’t full of with localhost URLs, my form fill history isn’t spammed with entries like “testtest123”, and my dev tools are (nearly) unadulterated by extension scripts.
- mnm1 8y agoThat's actually a huge part of why I switched and stayed with FF: their dev tools are now much superior to Chrome. No more clicking an XHR link in the console only to be taken to the network tab and have to manually locate that XHR. No more random caching of code even with 'disable caches' on. Among many, many other improvements. I would highly recommend giving FF dev tools another shot.