Plugging Internet Explorer's Leaks

jgwebber writes "If you're developing DHTML web apps, you probably already know first-hand that Internet Explorer has horrendous memory leak issues. You can't not run on IE, so you've got to find a way to plug those leaks. So I've created a tool to help you find them. So until Microsoft decides to fix its browser architecture (ha!), at least we can keep it from blowing huge amounts of memory."

Comments

Re:Not Microsoft's Fault

[ceeam]

You mean that in Korea only old people take a leak?

Not on the to-do list

[doublem]

It's all about features.

See, first you ball all of the security patches together, and have them all download, even if the user already has them. That way, because it takes longer and is bigger, they think it's a more substantial application.

Second, you add some new features. Like stealing compression code from Stacker, MS will just steal one of the "Tabbed browsing in IE" Plugins and muck the variable names up a bit.

Finally, you tweak the theme. You gotta make it LOOK like a new browser. This is more important than anything else. If it LOOKS the same, people will assume it IS the same. This is why the OS has gotten so much eye candy with each release, it's to make sure the users KNOW they're on a new OS by it LOOKING cooler.

But fixing actual bugs? There's no real Return on Investment on that, so it won't be done.