I do not consider that a MAJOR release - A major release to me would be upgrading the rendering engine, complete overhaul of code etc. Doesn't seem like they making a wize decision because they will now have several code treees (versions) to maintain and distribute patches to. Not even RAD methodology works this way.
Even on SVN if a patch is required for the javascript engine for example - then several life patches are required for each major version instead of one mainstream patch for one. It means it takes a lot more staff to maintain each supported release.
Already running on the Beta update channel, I'm started to hate the layout of the new Firefox, why has the home page button moved all the way to the right side of the menu bar
They're also trying to speed up the browser as Chrome can load webpages faster too. So sadly due to the faster development stage, some quality checks do slip away.
I think that is the biggest gripe people have had with FF in recent years, it has always been good from a features perspective (especially when you take addons into consideration) but they rested on their laurels a bit in performance terms, falling behind both Chrome and IE in that regard. I think what helped Chrome was they focussed on the fundamentals and making browsing a quicker more streamlined experience.
Might give this FF10 beta a go to see if they've made any strides in this regard.
edit: Just tried the SunSpider js benchmark (which I appreciate isn't the be-all and end-all of browser performance):
IE9: ~157ms
FF10: ~170ms
Chrome16: ~183ms
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.