Slashdot Mirror
Google Brings Chrome Renderer, Speedy Javascript To IE
A month after we discussed Google's bringing SVG to IE, several readers let us know that Google is expanding the beachhead by offering Chrome's renderer and speedy Javascript execution in an IE plugin. This effort is in service of allowing IE to participate in Google Wave when that technology's preview is extended in a week's time. The plugin, currently in an early stage of development, is called Google Chrome Frame.
In Firefox, this page [w3.org] shows "W3C Working Draft" along the left side.
It's not even complete, though. I think that's an optimistic assessment by them.
A lot of the features that Acid3 tests aren't new proposals in any sense; they've been around for years. WebKit (basis for Chrome and Safari), Gecko (Firefox and SeaMonkey), and Presto (Opera) all score above 90/100, which handily beats IE 8's 20/100.
That's not implying all of them are. IE is only supporting finished standards. There's nothing wrong with that.
The funny part is that Google is beating MS in their own game. They are actually improving the MS browser so that users can properly and smoothly use Google products
And if your browser's so screwed up that you can't even use Google properly, you know you screwed up, and you know you screwed up bad.
Seriously, the only code monkeys that could produce a browser that doesn't work with Google would have to be actual monkeys.
Let q be a radix > 1. I am in ur base-q, killing 10 d00ds.
I don't work off these lists either, but I'm aware of a numer of high profile parts of it, say, the Canvas element. I'm sure Microsoft is too.
A lot of the features discussed for HTML 5 have had visible implementations for 3-4 years. You could call them bleeding edge in 2006, maybe 2007. 2009? Not without looking pretty silly.
Popular doesn't mean standard. These are separate concepts. If it did, then every browser except for IE could be considered non-standard. Canvas is only popular within the enthusiast web developer clique, or "circle jerk" if you will. It only seems popular because you're part of a very *select* group.
These features will likely be supported when they're finished.
Can you defend this claim? Because based on my experiences *using* CSS over the last 7 years, there hasn't been a time when any version of IE could even claim they weren't maddeningly, brokenly worse.
Wow, since some snarky webtrash said it, it must be true. I tend to use the test suites when referencing this:
http://www.webdevout.net/browser-support-css?uas=IE7-IE8-FX3-OP9
The competing products seem to do just fine at keeping a comparable level of stability along with the pushing the envelope. In fact, given how much Opera, Mozilla, and Safari, have been able to do with resources that are orders of magnitude smaller, there's really no excuse.
Every other browser lags in enterprise oriented features such as group policies. IE has a clear marketshare in this case. It's also good at not being a moving target, so it is still favored by enterprises for things like intranets.
Yes, what would those narcissistic onanist web developers know about the relevance of the canvas tag to creating... web applications?
I don't see how canvas is relevant right now. It will be when it is finished, perhaps. For now, target Flash if you need that functionality. Right now, it's just another twinkle in the HTML 5 clique's eye.
I haven't gotten snarky yet, but perhaps I will when you explain what "webtrash" means. I certainly hope it's not your term for someone who actually has a working understanding of the issues we've been discussing.
Web trash = Web developers; not really designers, not really software engineers. Trendy, braindead, and useless in any real industry. They're responsible for such brilliant technologies as "ruby on rails" and other poorly designed frameworks that blow away collective millions of dollars of investor cash on energy and hardware in order to save them tiny amounts of time and make their code trendier. They're the sort of people who would complain that their job is too difficult because they have to target a conservative feature set based on the real-world deployment of unstandardized technologies.
That's *awesome*. With IE 8, we can now say that after 8 years of lagging behind, the browser created by the world's richest software company marginally edges out Firefox 3 in a feature-by-feature comparison CSS 2.1 features! Gives you a surge of pride, right? Why, if it constituted the most commonly used version of the product, that'd almost be the same thing as giving the world back all the man-hours spent trying to work around the support that wasn't there until this year!
Yeah, I was correct. Get over it.