3 ms·
So? 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
by ricardobeat 15y ago
So? 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.
- ok_craig 15y agoIt seems like everything you're talking about seems very specific to the kind of web work you do. As a professional web developer, I've never had these kinds of problems due to Chrome's or Firefox's rapid release schedules, and I've never heard complaints of it from other web devs. And the specific case you mention here is also something that could happen in a longer-term release; rapid-release lets you fix it faster.
- Silhouette 15y agoIt seems like everything you're talking about seems very specific to the kind of web work you do. Not being able to draw rounded corners properly is unique to "the kind of web work I do"? Yanking an entire video codec -- and probably the most popular one in the industry -- is unique to "the kind of web work I do"? Screwing up the browser if someone loads a page containing a Flash or Java applet is unique to "the kind of web work I do"? I'm honestly not sure at this point what it is you think I do or why you think it's somehow unique. I'm drawing on several projects and more than one client I've worked with here, and just about the only thing they have in common is that they involve building a web app rather than just designing a static page. There must be many thousands if not millions of guys doing similar jobs, and I'm far from the only person to report any of the issues I mentioned. And the specific case you mention here is also something that could happen in a longer-term release; rapid-release lets you fix it faster. Except that if your rapid release cycle doesn't allow enough time for adequate QA then it is far more likely that you will ship broken code, and in the plug-in case the breakage was so severe that they pushed an out-of-band patch to correct it anyway. The rapid release cycle may well have contributed to causing the problem and certainly did nothing to help fix it in that case.
- 15y ago
- ricardobeat 15y ago> 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 I think you missed the "standards" part.