Linked by Kroc Camen on Thu 25th Feb 2010 10:18 UTC
Humor BBC News reports "Mark your diaries for 4 March because in Denver the funeral arrangements are well underway for the planned passing that day of Internet Explorer 6". There's a phobia of being buried alive but I think in this case, it's the living that are all too quick to be shoveling the dirt over as IE6 doesn't officially die until 2014 when Microsoft pull the life-support.
Thread beginning with comment 411063
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: I like IE6, really
by Kroc on Thu 25th Feb 2010 20:13 UTC in reply to "I like IE6, really"
Kroc
Member since:
2005-11-10

IE6’s UI is what made it win over Netscape. IE6 was a breath of fresh air compared to Netscape. It wasn’t until Firefox was released that anything came along that was closely simple enough for IE6 users to want to adopt.

IE6’s toolbar is a good thing. What is wrong with IE6 is everything else. It’s slow, insecure and is a nightmare to code for. If IE6 had a decent rendering engine, then I would not find complaint with its UI. That is why ChromeFrame is a good thing.

Engine-wise; there’s still IE7/8, and IE8 is not too shabby and I really do hold out hope that IE9 will be a much needed return to a competitive IE.

Reply Parent Score: 2

RE[2]: I like IE6, really
by malxau on Thu 25th Feb 2010 20:51 in reply to "RE: I like IE6, really"
malxau Member since:
2005-12-04

What about "works with any browser"?

Like the original poster, I can't help but be bemused - an enthusiast site promoting operating systems diversity has become intolerant of browser diversity (at a time when to many, the browser is becoming the operating system.)

In any diverse ecosystem there will be "better" and "worse" participants (whatever that means.) The real issue here is not IE or IE6, but whether people believe that the web should be a platform that is open to anyone, or whether the web should be reserved for people doing the "right thing" (whatever that means.)

On a more technical note, HTML was designed to intelligently degrade when a feature is not present on the renderer. CSS2 really broke that, because if a style is partially supported the result may no longer be legible or correct. This, IMO, is what makes IE6 hard to support. The problem is not (entirely) with IE; the problem is that current web standards demand 100% conformance to have a useful implementation. This is not very open-web-like, and results in very rapid obsoleteness. It certainly discourages the web from being used in expensive hardware (car, fridge, whatever) because doing so demands unsustainably frequent replacement.

Reply Parent Score: 1

RE[3]: I like IE6, really
by Kroc on Thu 25th Feb 2010 21:18 in reply to "RE[2]: I like IE6, really"
Kroc Member since:
2005-11-10

Engine diversity is fine. Inconsistent standards implementation is not. If the GPU world was as messed up as the browser world, gaming would still be back in the 2000’s.

Reply Parent Score: 1

RE[3]: I like IE6, really
by google_ninja on Thu 25th Feb 2010 21:26 in reply to "RE[2]: I like IE6, really"
google_ninja Member since:
2006-02-05

Two problems.

First, there are loads of things that make the day to day life of a web developer easier. IE doesn't support a lot of them, while every other browser does a fine job with it. Supporting IE means you can't use those things, not supporting IE (but supporting every other browser) and you don't have that problem, unless you are talking about really bleeding edge stuff.

Second problem is that it is very buggy. Every browser has js and css bugs, but IE6 sort of took it to the next level.

As soon as IE6 goes away, it substantially raises the lowest common denominator (which will be IE7), and dramatically reduces the amount of hackery needed to get everything looking right.

Reply Parent Score: 2

RE[2]: I like IE6, really
by cerbie on Thu 25th Feb 2010 23:41 in reply to "RE: I like IE6, really"
cerbie Member since:
2006-01-02

Er, what about the random javascript error dialogs for CSS settings? Or that even when used with javascript properly, you could often get many dialogs in a row on a page load, or with an event on a dynamic page.

What about the crashing? That's never good, and it seemed to get more common with each hundredth added on to 4's release version number.

Personally, I preferred the Netscape UI. Even so, IE won that round somewhat fairly.

Reply Parent Score: 2