3 ms·
Chrome 32 really is a terrible update with some major regressions all over the place, all (apparently) for the sake of some custom scrollbars. To add onto the l
by Daiz 13y ago
Chrome 32 really is a terrible update with some major regressions all over the place, all (apparently) for the sake of some custom scrollbars. To add onto the list of issues, popup windows (including things like Chrome dev tools in their own window) constantly pop up a "Page is not responding" error, despite working just fine. Same for any Chrome apps that you might be running in their own windows.
I switched to Canary for the time being because 32 is just awful. Canary has saner scrollbars and also lacks the annoying slow zoom transition when opening dropdown menus (seriously, who the hell though that was a good idea). They really should hotfix the hell out of 32 ASAP.
Might just actually go back to Firefox one of these days, because Chrome is going into some annoying directions in general.
- scholia 13y agoI went back to Firefox 7 months ago. That was when it became better than Chrome: faster, more stable, consumes fewer resources, supports more tabs, better UI.
- frik 13y agoI still think Chrome peaked around version 20, I have an portable version of it around. With it I can open hundreds of tabs without any problems and it is perfect. Chrome 32 is so bad that I question the QA department/process of Google. Three days ago I Canary crashed on start (Win7) had to wait til next silent update, but now it's a lot better than 32. Firefox 26 is great, the only missing thing is multi-process support - otherwise a single website can hang the whole browser... not so good if you open dozens of tabs and keep them open for days.
- scholia 13y agoI think it was the Chrome 26/27 era that finally drove me away.... Understood re Firefox 26 multi-process support, but it makes a big difference to resource consumption. I've not had any problems but if necessary you could kill the browser thread and restart excluding the bad tab....