|
Quote:
This is like saying you'll give an A for effort when the student obviously still hasn't met course expectations.
|
More like not being a fan of repackaging the same thing under a different brand. Chrome = Webkit, it even has the same vulnerabilities.
|
IE will forever be a broken framework. Don't mark my words on this, but even developers have said it's probably impossible to bring Trident (IE) to the same place Gecko (Firefox) or WebKit (Safari) is without rewriting it from the ground up. A broken framework is a broken framework, and it may show substantial progress compared to any other browser today, but I'm not gonna use it just because the developers are trying. Call me back when it actually works.
|
I'm pretty sure thats just FUD. I don't ever remember reading that it's impossible to get Trident up to speed, and I check the IE developers blog pretty often. And besides, they got Acid2 from dogshit to perfectly working in one release, which tells me that Trident is as far from hopeless as possible.
Look at it this way: the IE team has to catch up with 5 years of webstandards. IE is progressing faster than other browsers, but other browsers have a hell of a headstart. But eventually they will catch up at this speed. As long as Microsoft doesnt pull the carpet from under them, like they did once IE6 won the first browser war.
Furthermore, IE still has nearly 70% usage, and new versions spread hella fast due to windows update - Firefox implementing a new css standard is a nice perk, but IE implementing it means we can start using it in webages the minute the new release is out in the wild.
This thing is sticky, and I don't like it. I don't appreciate it.