The organization put forward some reasonable arguments but ultimately backed down. The majority of respondents detested the idea (although a large volume of ranting and spam appeared when Mozilla’s intentions went public). Uproar ensued on Bugzilla and the associated newsgroup discussion. If you really needed the version number, it could be found in about:support.Users would be informed when the last check occurred, whether they were using the latest version, and how they could update (if Firefox had not automagically done so).One solution Mozilla considered was the removal of version numbers from Firefox’s “Help > About” dialog. Those using Chrome either understand this concept or don’t care. The browser also has fewer legacy hurdles and has silently updated since the early days. It’s add-ons system is far simpler more akin to bookmarklets than integrated code. Mozilla is replicating Google’s release model but Chrome does not necessarily exhibit the same problems. Few people understand the rationale behind major version increments. The majority of IT departments must test mission-critical applications before a browser update can be deployed throughout the enterprise. Most of us use extensions which cannot keep up with Firefox’s development progress. Most web developers agree it’s good for HTML5 feature evolution but it’s not without problems: Firefox’s rapid release schedule has not been the success Mozilla hoped.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |