All this takes maybe five minutes on Linux, on Mac OS X it will freeze the OS for long periods of time and take 40 minutes to run. In terms of hardware, the Linux box has less RAM, CPU and slower discs.
Regarding the Javascript stuff: Part of it may be that Chrome is the new Internet Explorer. People develop on and test for Chrome (because everyone uses Chrome, right?). Chrome does have the better Javascript engine, still, I believe that much of the slow Javascript on Firefox (an other browsers) could be avoided if people bothered testing a little more.
Chrome does have the better Javascript engine, still, I believe that much of the slow Javascript on Firefox (an other browsers) could be avoided if people bothered testing a little more.
All major engines are pretty much comparable speed-wise. The biggest difference is probably in memory management (of the HTML & JS engines), which may favor some forms of site/lib structure and architecture over others – that's IMHO where the majority of slowness comes from (for any browser).Afaik firefox still doesn't have OpenGL accelerated compositing (at least not enabled in stable builds yet) on linux
On OSX and Windows it has hardware accelerated compositing, video decoding, canvas etc...
Safari is the only logical choice on OS X laptops, at least. Everything else just eats up the battery like crazy.
I have to use Chrome for anything video related or JS heavy (monitoring/graphing stuff for the most part), but I'd hate to switch to it for everything. There are too many addons that I rely on in Firefox, on top of my general dislike for Chrome's minimalist UI and standard Google privacy concerns.
I've tried turning on the config option for electrolysis, but it breaks some addons, so that's still a no go for me for now.