IE8: Operation (now silently) Aborted
Since their post is somewhat confusing here is a dumbed-down translation:
Operation Aborted version 2.0
We are very excited about this change and think it is a huge improvement! We know that other browsers actually can handle those cases that cause this 'error' in IE but we do not know how to really fix it ourselves and because we do not believe in webstandards we don't want anything to do with for instance the HTML5 working group that is actively dealing with these sorts of issues, even though our own Chris Wilson (MSIE platform architect) is co-chair of that WG.
Yes, we know about HTML5 and have actually briefly read the working draft (but failed to comment on it even though we promised to do that almost a year ago), but we rather just cherry-pick from it and give it our own twist than actively participate in the WG and ask for advice or share implementation experiences.
Omdat een artikel engels is, moeten de reacties ook engels?
En sebazzz, de GUI van IE ziet er JUIST beter uit dan menig browser, functioneel is iets anders. ik vind firefox dan weer lelijk, maar weer functioneel. en IE werkt nog steeds prettiger met menig flash/video site.
GUI is a personal thing. You may think it's ugly, other people may think it's gorgeous.I dont get it why people still use IE... The GUI is ugly and imo not user friendly, IE uses much memory (compared to Opera and Firefox 3) and backend (engine) sucks as well.
And as far as memory use goes: FF3 isn't here yet. IE7 uses a lot less memory then FF2 does. So why is this an argument against IE?
Furthermore memory usage isn't so much of a problem as long as the memory gets freed up again, it's only memory leaks that are problematic and even though it is true that Firefox 2.x does have some memoryleak issues IE has them as well. In my experience Firefox is more stable over longterm use than IE is...
Comments are closed