A long time ago, Opera has released an experimental browser build that supports everyone’s loved hardware acceleration.
However, ever since then, there was little to no talk regarding estimated release date of the public build.
Data provided by StatCounter, a company that tracks browser usage using the free analytics tools it offers websites, shows that Chrome will pass Firefox to take second place right behind Internet Explorer (IE) no later than December.
Users and developers cited a number of reasons why consumers might want to use the less frequent Extended Support Release (ESR) builds that were announced recently. These include problems with extensions unable to keep up with the six week cadence, and a desire for fewer updates on machines they support for family and friends.
The ESR Firefox may also be just “good enough” for many users, one Mozilla developer argued.
The reason I expect a lot of users to switch to these ESR builds is not because they want extensions to work or because of any one issue that we can fix in the future. It’s simply because Firefox works ‘good enough’ right now and they don’t want to have to deal with change. – Cheng Wang on the mozilla.planning.dev discussion group
Remember how Mozilla rejected the faster Firefox release schedule (it was posted yesterday)? Well, here’s a new proposal and it goes like this: the Firefox release pace for enterprises is to be significantly slowed down. This should make corporate IT quite a bit happier.
If the proposal is adopted, Mozilla will deliver a new version of Firefox to enterprises every 30 weeks. That is five times slower than to consumers. During each 30 week stretch, Mozilla would issue only security updates for the browser. In addition, each enterprise edition would be supported for an additional 12 weeks after the release of its successor, assuring companies 42 weeks of support for each version. Continue Reading
A pitch to accelerate Firefox’s rapid release schedule even further i.e. shipping a new version every five weeks, was rejected by Mozilla. The proposal, made by Mozilla engineering manager Josh Aas last week, would have cut weeks from the current scheme.
Moving to a five week cycle would mean a fix going into mozilla central would get to users three weeks faster. That’s a big deal. It’s an upgrade in responsiveness that we can’t afford to pass on if we can pull it off. - Josh Aas, Mozilla engineering manager, on the mozilla.dev.planning forum
That’s how it should be done.
Here comes something exciting for all the Maxthon fans. In an effort to thank its users, China’s most popular web browser asks you to decide, what should be implemented next?
Here are all the available options:
- Lock Browser
Lock the browser to let others unable to see your web pages when you leave.