6 ms·
This is the one with a full silent update? Soon most people will be running one version of Firefox? Chrome + Firefox means 40%-50% of the Internet is getting
by melling 15y ago
This is the one with a full silent update? Soon most people will be running one version of Firefox? Chrome + Firefox means 40%-50% of the Internet is getting a browser update every six weeks. This will be a boon for software developers.
- mbrubeck 15y agoThe major change to updates in Fx12 is that the Windows UAC prompt will no longer appear for every update (by default). Some additional changes (like finishing the update in the background instead of at the next startup) are coming in a later version: http://www.brianbondy.com/blog/id/133/ http://www.brianbondy.com/blog/id/133/
- cpeterso 15y agoYou can disable Firefox's "an update is available" nag dialog with about:config app.update.silent=true. This pref has been available in Firefox for a long time, but I believe it wasn't enabled because people who don't restart their browser often would not get security updates in a timely manner.
- Silhouette 15y agoChrome + Firefox means 40%-50% of the Internet is getting a browser update every six weeks. This will be a boon for software developers. I never understand this argument. All we have now is two different fast-moving targets, both with a track record of introducing breaking changes. IME this just results in a significantly higher number of customers complaining to our customer support team (not Mozilla's or Google's) that our web pages/embedded UIs don't work properly any more. I have yet to be convinced that this obsession with releasing every six weeks really gets useful features out there in a way that benefits most users anyway. As far as I can tell, about 99% of the developers using those features are people writing tech demos for the browser makers and/or trendy web design blogs. Much of the content on those sites doesn't even work on both Gecko and WebKit at the same time, never mind IE. Meanwhile, real sites still have to cope with a majority of visitors who don't have the latest shiny new features. In any case, a lot of those features frankly aren't all that beneficial anyway compared to basic things like not freezing the entire browser UI because one tab is taking a while to load. That is something Firefox still can't do even though it's several years after every other major browser had it, and the apologists are getting awfully boring now.
- sciurus 15y ago"Meanwhile, real sites still have to cope with a majority of visitors who don't have the latest shiny new features." Umm, isn't that what the 6-week-automatic-update cycle that you're arguing against is intended to address?
- Silhouette 15y agoNo, because many people aren't using browsers that update every six weeks, and even those who are don't get the same updates every six weeks. In this case, as far as I can see, the only new "feature" they've shipped is actually to do with the update process itself, and it's a change that is pretty controversial at that. In fact, quite a few recent updates to Firefox (and Thunderbird for that matter) haven't really had much substance at all. Not exactly a great argument in favour of the need for such rapid updates.
- ok_craig 15y agoI wouldn't say there's a need for rapid updates; as a user, I just want them. I don't understand why users should be made to wait 6 months to a year for small features that are available now.
- Silhouette 15y agoAs a user, why do you want them? They are of no value to you unless sites or apps that you value are making use of them, and few production sites use most of the bleeding edge tech that supposedly justifies the rapid release cycle. A lot of that tech is of more interest for app-like pages rather than classical web sites, but then you start running into portability issues: not every browser has a fast cycle, and those that do aren't necessarily including the same features at the same pace. That means everyone needs to code a fallback approach anyway unless it's acceptable for their product to support only specific browsers. Once you start down that path, the core functionality is probably there for your users even if you don't then reimplement it a second time or add enhancements using the new technologies.