2 ms·
> Three monolithic releases in an entire decade is a better plan, you think? Strawman. I said no such thing. > The technologies involved with the web move too
by Silhouette 16y ago
> Three monolithic releases in an entire decade is a better plan, you think?
Strawman. I said no such thing.
> The technologies involved with the web move too quickly to still be thinking about IE 6 and IE 7 in 2011.
Ah, an interesting perspective of your own, I see. :-)
I need to support the platforms that my customers and/or my clients' customers are using to browse the web. Right now, I'm pleased to say that IE6 is no longer relevant to any current project I'm working on. IE7 still has enough market share to count, but most people I care about in relation to my commercial interests are now on IE8 or IE9. The pace of technology development matters far more to those of us writing web pages than to users, who typically only notice what browser they are using when something doesn't work, and even then only if it did work in some other context.
> All I can assume from that statement is that you're not a javascript or CSS developer.
Why? Because I have a different view to your own? I am currently working on several web-based user interfaces for different commercial projects/clients. They all work just fine in recent IE versions. At the most, we have graceful degradation for a few visual effects if you go back to IE7.
> Yes, about half of the world uses IE - mainly people who don't understand what a browser is, and click the big E on their desktop.
I think this is where we basically disagree. You seem to want to play with shiny new toys. I'm a shiny-loving geek too, but from a business perspective, I care about building useful stuff that benefits the web browsing public, and therefore either my own business interests or those of my clients. It doesn't matter at all to me why IE became the dominant browser for a long time, only that whatever functionality it provided was sufficient to do so. It is just a tool, serving a purpose, like any other browser software.
> IE is a deplorable web browser in the opinion of the vast majority of web developers I've ever encountered.
With due respect, what your web developer friends like isn't really the point. I care about users.
Are those users getting a significantly better experience using other browsers with rapid development cycles rather than IE? I have already listed several fundamental bugs that have resulted from the recent development processes at Google and Mozilla in my earlier post. Those bugs have in several cases visibly affected my or my clients' users. For all its ills, the reason IE6 lasted so long was that Microsoft never retrospectively screwed things up on that scale.
Meanwhile, since we're playing the "in my experience" game, all these fancy new technologies that are half-supported in leading edge Google/Mozilla browsers seem to generate far more heat than light, and I have yet to receive a single request from any client that would benefit from them, nor to my knowledge encountered any web site I use myself as a geek that benefits from them, with the possible exceptions of HTML5 <video> and <canvas>, which of course are only trendy substitutes for things we managed to do before anyway. (I have had to suffer using Google Docs with one client, and to describe it as unreliable, painfully bug-ridden, and missing the most elementary features that desktop office suites have literally had for decades would be rather kind. If that is the future Google are bringing us with all these new toys, I'll stick to tedious installers for Windows software, thanks.)
- magicalist 16y ago> I have already listed several fundamental bugs that have resulted from the recent development processes at Google and Mozilla in my earlier post. I see that you mentioned "broken" rounded corners and html5 video. (1) For border radius, if you were stung by the change, you would had to have been using the vendor prefixed version of the property, which isolated you from a breaking change in the final property. Feel free to blame that one on the CSS working group, for changing the definition, or yourself, for not planning for the possibility that an explicitly-prefixed experimental property could change before being finalized. Experimental implementations need to be made before a spec is finalized. You should absolutely use them, but only in circumstances where you monitor any spec changes and update your pages appropriately. If you can't, don't. (2) For the video element, you might want to actually test for a bug before claiming to have been bitten by it: h264 support hasn't been removed yet. h264-encoded videos will play just fine in chrome. Meanwhile full adblockers have existed in chrome for some time, and while tab isolation has been somewhat delayed in firefox, plugin isolation has done wonders for total crash rates. Finally, there's a point that is well worth repeating these days: the W3C requires working implementations for specs to become finalized recommendations. The fact that you can use the latest HTML5 and CSS3 features, even if their spec isn't finished yet, isn't some kind of nefarious plot, and vendor prefixes, as annoying as they can be, just mean that we won't be burdened later if specs change before they are finished. No one is forcing you to use shiny new things or experimental effects Stick to core functionality -- which I think you'll find all the vendors have done a great job at keeping from regressing -- and you'll be fine.
- Silhouette 16y agoI think you have misunderstood my examples. > For border radius, if you were stung by the change, you would had to have been using the vendor prefixed version of the property The rounded corners issue I talked about wasn't a mark-up issue, it was a basic rendering bug. It took several attempts to fix, over a period of months. During that time, any sites that used even simple rounded corners with an unfortunate combination of colours would get a horrible show-through effect or at best a poorly anti-aliased rendering in Chrome. Rounded corners were surely one of the most anticipated CSS3 features, just the kind of thing where a rapid release cycle is supposed to move the web forward according to advocates, and they regressed it, badly, for several months. Moreover, as long as Google and Mozilla keep releasing "experimental" CSS features with syntax and capabilities that aren't yet standardised, they are on a path where the only options are supporting alternative, non-standard functionality indefinitely or breaking existing web sites that were written using the experimental features at some unspecified point in the future. That's starting to sound like IE vs. Netscape all over again. > For the video element, you might want to actually test for a bug before claiming to have been bitten by it: h264 support hasn't been removed yet. Google dropped support for H.264 in the Chrome development builds some time ago, and the change is scheduled to be pushed to users of the official release imminently. > Meanwhile full adblockers have existed in chrome for some time, and while tab isolation has been somewhat delayed in firefox, plugin isolation has done wonders for total crash rates. If you've got a full ad-blocker for Chrome, I'd love a link. I've never found one anything close to as capable as things like Ad Block Pro in Firefox. As for tab isolation in Firefox, it's not just a robustness issue, it's also a performance and potentially a security issue. One tab loading slowly or running screwed up JavaScript can still block your entire browser for several seconds, which can be very annoying. > Stick to core functionality -- which I think you'll find all the vendors have done a great job at keeping from regressing -- and you'll be fine. No, they haven't. I have given you four specific examples, and while you could argue that the two Chrome ones (CSS3 rounded corners and HTML5 video support for H.264) were experimental, there is no denying that the two Firefox ones (Java applets and the basic typography engine) are fundamental, well established, and seriously broken in several recent Firefox 3/4 builds. Please check my posting history from a few weeks ago for details; I gave specific citations to the last guy who seemed unable to believe it. Of course, if you're going to argue that we shouldn't worry about any problems with experimental features, particularly either regressing them or cutting off support when a standardised alternative becomes available, then you're basically undermining the entire premise of this discussion, which was that rapid release cycles advance the web more quickly. As I've been saying for a while, I don't think going back to the race between IE and Netscape is going to advance the web for users in any useful way. It's just going to create a nasty, half-defined mess that most developers are going to ignore most of the time anyway, and that breaks things in user-visible ways the rest of the time.