Posts Tagged ‘IE’

Your money is safe with us (javascript error)

Thursday, March 27th, 2008

I’m on the team that develops a stats package for our product at my job. It’s a web app showing all the activity on the customer’s website. At the beginning of the project, we decided that we didn’t want to spend the time to hack the code to work in IE6, so we set the system requirements at FF2+ and IE7+. (No Safari either, but that’s a separate issue.) Any web developer will tell you that 40-50% of the time it takes to build a website is spent making the thing work in IE. IE sucks.

This was all well and good, since at the time of this writing IE7 has been out for about 14 months and has been easily available via Windows Update to anybody with an internet connection.*

Then it bit us. One of our customers is some bank in Nebraska or Kansas or some other flyover and they only use IE6 and therefore can’t access the stats program. “Sorry, we don’t support IE6.” “Well, we need it to work and we aren’t allowed to upgrade or download any other browser. Please fix.”

There are many places I wouldn’t keep my money: on the trunk of my car; in a fireplace; hidden under my porch; mixed in with the cat food. However, I would feel much safer with my money in any of those places than in a bank that only uses IE6 on purpose.

* I’m not advocating IE to anybody. Not even a little. It is the most awful software every to appear anywhere. But if you have to kick yourself in the balls everyday, you might as well do it wearing the newest shoes possible.

This just in: IE sucks.

Friday, October 5th, 2007
IE architectChris Wilson…IE Mastermind
and WWF stunt double

I read this article featuring an interview with the architect (mastermind) behind MS Internet Explorer. This is one architect I wouldn’t hire to build my front porch…out of fear that my porch will need critical updates every week to keep my neighbors out, or to keep it from crumbling my house for no good reason.

Things of note: the interview started with Windows crashing. I’d comment on that, but it’s just too easy.

IE6 didn’t display semi-transparent PNG files correctly. He admits to the problem “we have certainly some problems with PNG files in the past” but then goes on to say that the problem was confined to “narrow cases”. Narrow cases? If you consider the main advantage to using PNG format “narrow” then that’s true.

He then defends the uber-tight integration to Windows, which is what it is. Doesn’t really matter. Apple does the same thing with Safari and WebKit. The problem comes when the security of the browser is so shitty that you can remotely catch the computer on fire. Not good.

Why is the IE7 download over twice the size of Firefox? He claims “backward compatibility”. Huh?

The big challenge for us is we don’t run on just one version of Windows. We can’t rely on things that are just in Windows Vista.

A lot of the things that make IE larger are really that it’s delivered as a set of system services that are essentially atoms for Windows. You can use just parts of the browser. It’s componentised very specifically so you can do that.

So his answer to backward compatibility is just to ship extra parts of Windows with IE7? That seems a bit strange. FF doesn’t need to ship extra parts of Windows.

Here’s the best part. When asked about why, after 10+ years, IE still doesn’t support the W3C standard he says this gem:

I’ve spent a lot of my career working on developing standards with the W3C, and unfortunately they’re not that well-defined the first time out.

Oh, so the reason IE sucks is because the standard sucks. Got it. And the reason IE doesn’t follow the sucky standard is because the standard sucks. Yup. This sounds exactly like an error message I might find in just about any corner of Windows.

We may have done something that wasn’t really clearly specified in the specification. We need to change that in a browser release, but the behaviour we used to do is already out there. Once we do that in a new browser, we break a lot of content if we’re not very careful.

In other words: “We did our own thing and made a shitty product in spite of the spec and people made shitty sites. So now if we make a good product, the shitty sites, which are our fault, will break. It’s very important that sites not break because of IE.” What a fucktard.

Why no plugin architecture for IE? Cuz it’s too hard:

Firefox has a really great user community. Microsoft wouldn’t do that, though, because it would make troubleshooting so hard.

Outstanding.

The best part: he looks like a pro wrestler.

More browser fun: