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."
why should i care and spend my precious time about the memory usage of my damn webpage for IE users ?
just let them feel how bloated and buggy it is, so they switch to mozilla/firefox
same here. Firefox user for the last year or so [mozilla before that] on my Gentoo only boxes.
...
Despite what the "leading authorities" [of premium quality bunk] think you can happily browse the net with just about anything other than IE.
This whole "I gotta write for IE because people use IE" is not only depressing and self-fulfilling but a complete fucking lie. I know many windows users who use Firefox in place of IE on a regular basis.
The problem is these "authorities" are uneducated webpage slingers [I'm old enough to be into computers when putting a web page up wasn't a career but just something you did as part of another job...] who grab hold of a single tool, learn it to a certain degree than call themselves experts. Right up there with "Java is the best tool in the world!!!!" types
Sad as it is to say my College experience was at least productive in the aims of countering this tendency. In my web development class [as part of my comp.sci program] we developed pages and back ends [perl CGI] that had to work for both MS IE [5.5/6.0 at the time I think] and Netscape.
Tom
Someday, I'll have a real sig.
I have a better idea. There should be a worldwide law that states that all websites must make every effort possible to crash MSIE, but run well on all other browsers. The reasoning is that by eliminating MSIE, much of the risk associated with cybercrime will disappear with it.