News for hackers. Stuff that matters.
Re: Is IE8 already a legacy browser? Google thinks so. by code_duck on Saturday May 21, 2011 @07:34PM (#2572103)
Interesting perspectives. Let's see.

>I still don't understand why people think this crazy rush to get new browser versions out as rapidly as every couple of months is a good thing.

Because the alternative system involves way too much pain in upgrading for users, apparently. Three monolithic releases in an entire decade is a better plan, you think? The technologies involved with the web move too quickly to still be thinking about IE 6 and IE 7 in 2011.

>While Microsoft's release cycle is perhaps longer than I would choose, at least they have some stability as a result. We may have hated IE6, but we did so only after several years of it being clearly the best browser in town, which people often forget. In any case, at least its quirks and foibles were well understood, and workarounds were widely documented and used basically successfully. Ditto for IE7, and anything from IE8 onwards is pretty decent as far as web standards go.

All I can assume from that statement is that you're not a javascript or CSS developer. IE 6 was the best because Netscape had their 'air supply cut off' and was not really in the game in 2001. IE 6 and 7 continue to cause problems for me, personally, and if I was the only one, we would not be having this discussion.

>For all the anti-IE criticism, the Web developed from a novelty to a routine part of daily life on Microsoft's watch, and about half the people in the world still use IE to get stuff done, despite all the possible alternatives available to them.

Yes, after MS beat down the company who pioneered bringing browser technology to the masses, the web grew while IE was the most popular browser. 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. Including software with other software that has monopoly level market saturation is successful, can you believe it?

> I'd rather the Chrome and Firefox teams caught up with basics that most people actually care about: Firefox 4 still doesn't do sensible tab isolation years after IE and Chrome did, while Chrome still doesn't seem to have an ad blocker worth anything, for example.

IE doesn't even have a spell check, much less an ad blocker. How about Web GL? If I recall from the Reddit threads from the IE team, Microsoft insists they can't put IE9 on XP mainly due to hardware acceleration. For 2D only?

>Please note that none of this means they can't issue security or performance updates as necessary. But Microsoft do that too, they just don't feel the need to slap a big "this is a shiny new version!" sticker on it every time.

How many significant updates to IE 8 have there been? How often was Chrome or Firefox improved during that time, noticeably? Waiting until MS releases a new version of Windows and everyone buys a new computer in order to run it has left web developers with a lot of problems.

>the vast, vast majority of the world's IT infrastructure still lives in the desktop software era, and most web-based or mobile-based software sucks on technical, usability and basic functionality grounds.

Some people are still using DOS, but that's not really the point. I expect at some point, the enterprises who haven't already figured it out will realize that developing or purchasing inflexible, monolithic software that is upgraded with great pain and expense every five years is not ideal. Hundreds of millions of people are using internet based software (and I'm not talking about Google Apps - I mean applications such as this site) each day, and they work. Meanwhile, I can't open an IT magazine without seeing the word 'cloud' 8,000 times, so... we'll see what happens to the world of desktop software, hmm?

IE is a deplorable web browser in the opinion of the vast majority of web developers I've ever encountered. it's the only one that you have to fire up virtual machines to test on three or four different versions even when using Windows. The development models of webkit and Mozilla have resulted in far superior software, and that's really all one can say. It's time for MS to either get serious about releasing a top quality browser, or go away.

Re: Is IE8 already a legacy browser? Google thinks so. by code_duck on Saturday May 21, 2011 @08:06PM (#2572178)
>Strawman. I said no such thing.

You say Google and Mozilla are moving to fast, MS is doing things right. So...?

> Ah, an interesting perspective of your own, I see. :-)

Yes, I think people should upgrade their browsers more than once every 4 or 5 years. Call me crazy.

> 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.

When I spend an extra five days getting a project right in IE, or writing a totally separate version for this browser, yes, users are being deprived of something useful I could have done instead. When IE's quirks and flaws cause my page to not work, users notice something didn't work.

> Why? Because I have a different view to your own?

No, because you said IE 6 and IE 7 are essentially trouble free.

> I think this is where we basically disagree. You seem to want to play with shiny new toys.

Yes, I don't want to have to cobble together a separate version for some browser from 8 years ago. Again, IE is the only one that works anything like this.

>With due respect, what your web developer friends like isn't really the point.

Thanks, but actually it is since we're discussing my opinion and the opinions of developers. I thought.

> I care about users.

So do I, I'd like for them to have my software in a more performant, more reliable form, more quickly.

> 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.

You seem to have no concept of how the long standing, never fixed bugs and design flaws in IE 6, 7 and 8 have affected users.

> For all its ills, the reason IE6 lasted so long was that Microsoft never retrospectively screwed things up on that scale.

No, IE 6 lasted that long because MS didn't update it for six years, and then tied the new version to a widely disliked OS. Developers were forced to bend over backwards to support IE 6 due to it's continuing market share. MS never 'messed it up' because they never even tried to improve IE 6 between 2001 and 2006.

> 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>.

So, none of your clients expect high performance JavaScript. IE 9 is still remarkably slow compared to every other browsers.

I've had a hard time finding IE enthusiasts other than corporations, neophytes and MS developers. It seems rather apparent you fall into the latter category.

Re: Is IE8 already a legacy browser? Google thinks so. by Silhouette on Saturday May 21, 2011 @08:16PM (#2572206)
I'm sorry, but you're still just producing strawmen. I don't like coding for IE, I just don't like coding for fast-moving targets that keep introducing bugs either.

Also, you seem to have an awful lot of serious problems with older versions of IE on your projects. Spending days getting a project right in IE? Writing a totally separate version? Long-standing bugs affecting your users in visible ways? User-visible problems with JS performance in IE9? Some of those were certainly problems with IE6 and to some extent with IE7, but if you're really still suffering those problems with IE8 -- the topic of this conversation, and the latest version supported on all popular Windows versions -- then I have to think that either you're in a remarkably specialised field or you're doing something wrong.

Re: Is IE8 already a legacy browser? Google thinks so. by code_duck on Sunday May 22, 2011 @02:46PM (#2573910)
I hope I'm not getting carried away in this discussion, given my passion for the topic and disappointment in IE. Apologies if so. I suppose you see cutting edge as frivolity, but yes, IE is entirely incapable of the more advanced and interesting things that Firefox and Chrome can now do. Hence, one might write a degraded version for IE, or a separate version in Flash. The thing is, all other browsers are very good about getting their users to upgrade, so I don't really think about a degraded Firefox, Safari, Opera or Chrome version. S I've coded myself into corners testing with Firefox and Safari, then had to redo it a lot for IE to work. Maybe it's just mainly painful memories from when I was starting out. About 4% of our users are using IE9 currently, so I haven't heard much user feedback about the JScript speed. I do hope everyone upgrades soon, of course. I don't work for an enterprise, and I am the only full time developer in my (micro) company. With everything I have to do, testing in 5-6 versions of IE has been a big problem for me in the past. Given that my experience does not seem to be isolated or anomalous, I don't think I'm doing anything wrong. Perhaps Google and Mozilla have made mistakes, and update too often - but their situation is so clearly superior to Microsoft's, who can't even figure out how to get some people to upgrade from a browser released 10 years ago, that it's clear which system is working better. As usual, the ideal style lies somewhere in between.
Re: Is IE8 already a legacy browser? Google thinks so. by Silhouette on Sunday May 22, 2011 @06:13PM (#2574376)
Now, most of that I can agree with. I have nothing against moving the industry forward, and of course I wish all my users and my clients' ones would upgrade in timely fashion.

My main observations in this discussion is simply that moving the industry forward only works if it's done at a pace where the content providers can take advantage of it. Personally, I don't for an instant believe that Google's and now Mozilla's release schedules with only a few weeks of gap help to achieve that goal. Meanwhile, they can and have screwed things up that have worked fine for years and are in widespread use on web sites today, and I think they are in real danger of reverting to the completely non-standardised web of yesteryear, which makes developing corner cases specially for IE look like a walk in the park.

For what it's worth, I find it even more disturbing that even so-called standards groups, particularly WHATWG, now seem to be moving to "evolving" documents. They seem to have utterly missed the point of what standards are for.

As you've probably realised by now, I'm no worshipper at the altar of Redmond either. I do wish they would consider releasing faster than every couple of years, and I don't buy their nonsense argument about IE9 being unable to run on XP for a microsecond. (What they say may well be technically true, but it smacks of the kind of arguments they made a few years about during the anti-trust case, that they can't possibly separate browser from $OS because of $DEPENDENCY, where $DEPENDENCY appears to have been easily avoidable if they'd coded things up a bit differently.)

Re: Is IE8 already a legacy browser? Google thinks so. by 911-inside_job on Saturday May 21, 2011 @08:17PM (#2572209)
Re: Is IE8 already a legacy browser? Google thinks so. by code_duck on Saturday May 21, 2011 @08:28PM (#2572235)
Great, if after ten years of trailing everyone else by orders of magnitude they're going to take the lead I'd be thrilled and quite impressed. Benchmark results do have a way of changing by the time products come out of 'preview releases', though.
Re: Is IE8 already a legacy browser? Google thinks so. by Silhouette on Saturday May 21, 2011 @07:55PM (#2572148)
> 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.)

Re: Is IE8 already a legacy browser? Google thinks so. by magicalist on Saturday May 21, 2011 @09:59PM (#2572389)
> 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.

Re: Is IE8 already a legacy browser? Google thinks so. by Silhouette on Sunday May 22, 2011 @07:28AM (#2573082)
I 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.

Re: Is IE8 already a legacy browser? Google thinks so. by magicalist on Sunday May 22, 2011 @07:23PM (#2574543)
>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.

You're going to have to point to a bug report, because I don't know what you're referring to. Webkit had poor rendering of border-radius with a varying radius (the edge would be discontinuous), it had an issue where box-shadow would break with rounded corners, and it had an issue where the element background color would show show up slightly outside of any border color. All were bugs, but none were regressions, as far as I know.

> 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.

That's just the reality of web development. We should have had a stable foundation for content, styling, and scripting for a decade now, but the standards are now finally being advanced at a decent rate. In order to do this, we need both experimental and working implementations. You'll note that Opera has -o- prefixed css properties and Microsoft has -ms- prefixed properties. That's how it works...implementations are built while specs are being written, but nothing is standardized until interoperable implementations exist. For more: http://www.alistapart.com/articles/prefix-or-posthack/

> 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.

You're making me second guess myself, but AFAIK, they didn't and it isn't. The announcement was that they will sometime soon, but that was to give people time to switch. I was just able to play h264 videos in dev and canary builds on my windows and mac machines.

> 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.

There's "AdBlock" and "AdBlock Plus." I think the second is made by the same guy that makes AdBlock Pro, but I don't really keep up with it. I have click to play enabled for plugins and that'sufficient blocking of annoying things for me.

No idea what's up with applets, but the irony of bringing up the font rendering change in Firefox 4 is that Firefox 4 was a long in development, monolithic release. Whether the style of font rendering is a regression or not is up for debate (there were also tradeoffs that had to be made working with GDI and directx), but really it's just a change people don't like, which has nothing to do with changes in release rates. UI and UX regressions happen all the time; that's why it's great to have a choices.

Finally, there are two points here: 1) Only use experimental features if you're willing to be a participant in the process, even if that just means keeping up with implementation changes 2) Point (1) would only prevent quick release cycles from advancing the state of the web if implementations didn't converge and specs weren't finalized at a rate faster that e.g. IE's release rate. They do, and since HTML5 and CSS3 have moved to a more modular spec format (rather than the decade long process for CSS 2.1), we are going to see the effect of a lagging IE10 over the next two years.

All that said, legacy browsers will have a worse effect, so it's really not that bad. I'm not saying that Microsoft is bad (although required browser updates after, say, 3 years with only an opt-out option would make me a happier camper), I just think that the faster release cycles are better for the web (for developers, users, and advancing web standards), and that the growing pains we've experienced have actually been quite minor.