6 ms·
Chrome + 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 thi
by Silhouette 15y ago
Chrome + 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.
- ok_craig 15y agoBrowser updates are more than just html/css/javascript functionality updates. For examle, if Google updates the UI of Chrome and they can push it to me now, why not? I don't want to wait, and Google is giving me the option of not waiting. Or if they update their extension APIs and I want to make or use an extension that relies on them - why wait? Or if they make javascript run twice as fast for me. As a user, I love being able to get those things as soon as they're ready. > That means everyone needs to code a fallback approach anyway unless it's acceptable for their product to support only specific browsers. This has been and always will be true until 100% of the web uses the same browser. I'm not sure what the point of stating it is, or how a rapid-release schedule makes it worse. It doesn't.
- wickedchicken 15y ago> 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. Security updates.
- Silhouette 15y agoIf it takes six weeks to push a security update, you're doing it wrong. This is part of the problem with the fast update cycle: People are now conflating security updates (which should be out there ASAP and should make no functional changes at all) with functionality updates (which are never necessary unless you want to visit a site that uses a new feature or to use some change in the UI, have a much higher risk of unintentionally or intentionally breaking stuff that used to work, and certainly don't need to happen 8-9 times every year in any case).
- yuhong 15y agoSecurity updates already existed before Firefox went to the six-week release cycle, and there is now the ESR branch with security updates only.
- drivebyacct2 15y ago>In any case, a lot of those features frankly aren't all that beneficial anyway You're clearly not on the edge of new experimental features or you wouldn't be making such a claim.
- Silhouette 15y agoYou couldn't be more wrong. I make my living building web sites and embedded browser-accessible user interfaces, and several of the projects I'm working on right now use state-of-the-art features with HTML5, CSS3, mobile devices and all that jazz. And I stand by my previous comment despite that.
- drivebyacct2 15y ago>state-of-the-art features How can you claim to use state-of-the-art features and not appreciate that those features will be more stable and more readily available than ever? And the cool new features being worked on are far, far, far more expansive, neat and "useful" (as you desire) than "css3" or "mobile devices". If you're really doing "state of the art" things, then you're probably using features that were added to Chrome and Gecko as part of one of the features that was enabled by the rapid release cycle with multiple versions and pipelines being worked on simultaneously. Further, what breaking changes have you seen as a result of Firefox and Chrome's rapid development cycle. I mean, the features I'm discussing break regularly, but then again their specs are still in a very draft status and it's known that they will break. I can't say I've ever had a stable Javascript API or CSS rule just completely change when moving from Firefox 11 to 12 or whatever. >"Much of the content on those sites doesn't even work on both Gecko and WebKit at the same time, never mind IE." Honestly a lot of your claims seem to be exaggerated or I'm on a very different subset of the Internet than you.
- Silhouette 15y agoHow can you claim to use state-of-the-art features and not appreciate that those features will be more stable and more readily available than ever? Because they aren't more stable and readily available than ever. Browser fragmentation is worse today than at any time in history, including the peak of the Netscape/Microsoft war. At any given time, you might have to implement a given bit of styling at least three or four times over, not because the browsers differ in their functionality, but just because they all do it with slightly different syntax. That in turn is because the browsers frequently have slightly different ways of doing things first, even if someone then wins later, which of course means everyone else has to slightly change their behaviour to match whichever standard wins. And that's before you even consider the standard refrain that "it's all beta, we can change the APIs at any time, this functionality shouldn't be relied on for production sites, yada yada". And then you have to consider the bugs, of which there are many in bleeding edge features, not helped by the fact that the six week release cycle is demonstrably too fast for a reliable QA process for software of this complexity. And even when you've taken care of all of that, you still have to consider the fallbacks for older versions of IE, graceful degradation for mobile devices with limited bandwidth, and so on. Further, what breaking changes have you seen as a result of Firefox and Chrome's rapid development cycle. I mean, the features I'm discussing break regularly, but then again their specs are still in a very draft status and it's known that they will break. I can't say I've ever had a stable Javascript API or CSS rule just completely change when moving from Firefox 11 to 12 or whatever. Lucky you. We're lucky if an update ships and we don't get someone finding a bug somewhere. Right now, for example, Chrome has taken so many shortcuts to try to improve responsiveness that it's just plain broken when it comes to refreshing the page layout or even just repainting in timely fashion after a DOM or CSS change. That means even popular UI toolkits have trouble with basic things like displaying dialog-style content, an everyday task if you design browser-based UIs. And because it's not repainting properly in the first place, presumably because some internal events aren't invalidating some cached data they should be, there's no clear workaround nor any guarantee that you'll get the same breakage from one update to the next. Another example for Chrome from a bit further back was the way they completely stuffed the drawing of rounded corners. And then stuffed it again, in a slightly different way, in the next update. And then stuffed it again, a different way again, the update after that. Then there's the whole H.264 question. Is it supported or not? Officially it was going to be dropped quite a while ago. And then it wasn't. And then maybe it is, but actually on Windows it works anyway because of someone else's software. Moving on to Firefox, when they pushed out the LTS release a few weeks ago, they included a bug that basically stuffed every site that used such obscure technologies as Flash and Java applets. That bug was known about several days before the update went out, but they pushed it anyway. Having established the scale of the screw-up, they then proceeded not to undo the update until they had a fix, which took several more days. On behalf of the customer support guys I work with who were flooded with complaints that our user interfaces had stopped working for about a fortnight, I'd like to thank the people at Mozilla for instituting such a robust and user-focussed QA process along with their rapid release cycle. I could go on (and on, and on), but right there you have several real world examples of rapid releases pushing out fixes that broke fundamental, widely used technologies, both old and new. Honestly a lot of your claims seem to be exaggerated or I'm on a very different subset of the Internet than you. It's funny how often I hear that. And yet two minutes with Google searching for information about any of the bugs above will turn you up thousands of references. And I'm being kind here and not even picking on all the little details they keep breaking in more bleeding edge features, nor on all the irritation to end users rather than developers that both Mozilla and Google cause when they subtly change their UI around for no particular reason.
- melling 15y agoNo one is saying that the day a feature is released that it will be widely adopted. CSS animations, for example, can be incorporated in sites, and as performance improves, etc it will become more widely used. Some "features" are simply performance improvements (e.g. GPU acceleration, better JS JIT, WebGL improvements; Chrome added software WebGL support on the last update). Developers will be able to clean up their CSS more often (e.g. -webkit-border-radius, -moz-border-radius => border-radius). Sure, somethings will be only for developers at first but after a burn-in and Chrome/Firefox adoption, certain features and techniques will become mainstream. IE users will get the more "generic" page. Not a lot can be done about that. Finally, let me add that it reduces testing for developers because now you only have to test on one version of Firefox. FF 3.6 is under %3 market share, and it was retired today. As for the not freezing, that's a different unrelated issue. I've been running the Firefox and Chrome nightly's for a year and I'm pretty happy with both.
- Silhouette 15y agoI understand what you're saying, I really do. I just think we would do better as an industry -- in the sense of producing more real world projects that benefit real world users sooner -- if instead of everyone having an anatomical measurement contest about version numbers, we slowed down the pace of releases but tried to standardise the useful new features within a release cycle or two. There is no advantage to anyone in having essentially the same feature available in, say, Gecko and Webkit, but subtly different syntax so all the CSS has to be written twice. There is no advantage to anyone in having HTML5 video, but Google being unable to make up its mind about whether H.264 is the de facto standard because it's better than everything else or the spawn of Satan because of the patent concerns. And so on...
- melling 15y agoThat again a different problem unrelated to rapid updates. Yes, I agree it would be great if everyone converged on standards sooner. If we agree on the one true standard to create a linear-gradient, for example, then we shouldn't have to wait 2 years to get it implemented. Btw, you are supporting all those Opera extensions too, right? :-(
- ricardobeat 15y agoSo? If you ignore the "shiny new features", it doesn't make much difference if the updates are 6 weeks or months apart. They are not fast-moving targets because the already standardized technologies don't change. Pages render 99.9% alike on Chrome 4 to 19, same goes to FF > 3.5.
- Silhouette 15y agoIf you ignore the "shiny new features", it doesn't make much difference if the updates are 6 weeks or months apart. They are not fast-moving targets because the already standardized technologies don't change. Oh, if only that were true. The number of minor issues that Firefox and Chrome have broken in their rapid updates is vast. And they break major things occasionally too. Try looking at what happened to pages using Flash or Java applets in (ironically) the initial LTS release of Firefox a few weeks ago, for example, or consider the Chrome/H.264 fiasco. Leaving aside the things they are breaking, there is also the issue of things they are not fixing. There are plenty of long-standing and widely applicable bugs in the rendering of existing but no longer trendy features in these browsers. I don't see how you can have this constant pressure to show progress and support for bleeding edge technologies without also squeezing out developer time that would be better spent fixing bugs that already affect many users today.
- ok_craig 15y ago> The number of minor issues that Firefox and Chrome have broken in their rapid updates is vast. What exactly has lead you to this conclusion? As a professional web developer for a high volume website, I can't remember a single instance of Chrome breaking any html/css/javascript on our site between updates. That's not to say it doesn't happen, it just seems really rare and minor... What kind of site do you develop that users are constantly complaining that things are breaking due to Chrome updates? I've never heard this be made as a sincere complaint before.
- Silhouette 15y agoPlease see my other posts in this thread for some examples. The case I was specifically thinking of in that case was the Firefox bug that broke Java applets a few weeks ago, and with them everyone's web apps that use the technology as part of their UI.