IE7: Not Much Better…
Joel Webber posted about the supposed fix-all security update released by Microsoft for IE.
Of course, it doesn’t fix all, as demonstrated here. Shock!
This totally jibes with my recent misadventures with IE7, when I found out that one of Microsoft’s “clever” workarounds is to add an artificial limit to 32,767 Javascript statements in a given scope – yes, I managed to generate this many statements as the result of including Javascript generation in a template system.
Also, note that their arrays are limited to 32,767 elements. I’ll bet that there is more of this stuff in IE7.
In a nutshell: Microsoft fights memory leaks by breaking existing scripts and doing a bunch of hasty cleanup when unloading a page.
But that’s not even what’s annoying me the most. No, it would be this: http://support.microsoft.com/kb/933873
In this knowledge base entry, Microsoft acknowledges the issue and informs us that a hotfix is available; all we need to do is call them and maybe they will even wave the support fee, should they “determine that a specific update will resolve your problem”.
So, what are we to do? Call our customers and instruct them to see if Microsoft is willing to send them a patch, for free or not?
***
We recently stumbled upon a couple bugs in Java 6. More specifically, in rt.jar. Sun wasn’t exactly in a hurry to fix them. So, we fixed them ourselves.
As developers, do we really need more reasons to embrace open-source? I do not think so.
Similar Posts:
- Management – is this leadership?
- Microsoft finally gets its way in Europe
- Open Source: A Common Misconception
- PHP classes and Javascript: S2ajax says “hi()”
- Open source web apps *do not* suck.
If you enjoyed this post, make sure you subscribe to my RSS feed!
If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.
Comments
No comments yet.
Leave a comment