Slashdot Mirror
Google Brings SVG Support To IE
stelt writes "Scalable Vector Graphics (SVG) is in most graphical tools. It is used heavily in many big projects, such as KDE and Wikipedia. But Internet Explorer's lack of built-in support for SVG was keeping it away from mainstream use on the web. Google is fixing that now with a JavaScript drop-in named SVGWeb. They've posted a quick, one-minute overview, a longer and more detailed presentation, and you can read about it on the project page."
How long before a new version of IE develops incompatibility problems with this extension?
Now Microsoft doesn't need to do it anymore. Is this a good thing then? Nice move on Google's part though.
It's a bad thing that Google needs to fix basic functionality in a competitor's product. But it shows one more time why Google is good and why Microsoft is mediocre.
That plugin was always slow and only supported a very limited subset of svg.
A fool throws a stone into a well and a thousand sages can not remove it.
... the long-awaited dawn of SVG animation challenging Flash, (and Silverlight)?
Microsoft is becoming AOL. A crappy, proprietary, expensive, unreliable impediment to getting onto the internet. Their applications have plateaued, and open-source desktop and web-based competitors are improving rapidly. They'll hang on longer, but they've begun their long decline.
If you look at Silverlight (or XAML or XPS) you'll see a lot of things that resemble SVG. It would be trivial for MS to support SVG, but they choose not too. The probably don't want anything to compete with Silverlight adoption.
Wanted: witty unique signature. Must be willing to relocate.
Sorry, I once worked on a site, where we got 16 million visits *a day*! And that's only for the top country.
Yeah, we've all "worked on" big sites. It's quite another thing to be financially accountable for a big site. You'll find it's a little less easy to cast away 10% of your users overnight when your profit margin is only 1% to 3%.
The proper way to build a big site is to build to standards and then add exception handling for any significant user bases. Over time some of these will shrink below the "who cares" limit and you can get rid of that exception. Obviously those limits will vary per site and audience.
Your rant about leadership is fine, but you do not lead your customers, you serve them. You lead your employees, and then, yes, you sometimes make decisions that are necessary but not popular.
Build a man a fire, he's warm for one night. Set him on fire, and he's warm for the rest of his life.
Even supporting IE at all means withholding features. That can make sense for supporting IE 7/8, which hold about 40% of the browser market.
IE6 only holds about 15% of the browser market, and requires extreme measures to support. If Google, a 150 billion dollar corporation, can't be bothered to support it in something as simple as a webmail client or video portal, why should the little guy struggle to support it in a complex web app?