|
More like not being a fan of repackaging the same thing under a different brand. Chrome = Webkit, it even has the same vulnerabilities.
|
The new WebKit spec passes Acid3 100%. I'm sure Chrome will eventually use this spec, as this was after all a beta release. Why fix what ain't broken?
|
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.
|
It was before the IE7 release so maybe that's why. It was at least one year ago, more than likely two.
|
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 doesn't fix the fact that IE is broken
right now. Furthermore IE has more like 50% usage, split between IE6 and IE7. This doesn't mean IE8 will have complete 50% usage because not everyone will upgrade. There's still a fair amount of people who probably use IE6, and there will be a fair amount of people still using IE7, so the actual usage stats will probably be more around 18% for IE8.
I dunno, I think Chrome has more potential than the flawed IE engine ever will.
I am a dolphin, do you want me on your body?