Linked by Thom Holwerda on Wed 6th Jan 2010 20:01 UTC
Permalink for comment 402888
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2006-01-03
Long time ago, I was extremely excited when SVG was introduced and first implementations in browsers (excepting IE, of course) started to show the potential of documents enriched with SVG: Animations, diagrams that looks quite professional without having the need of high resolution bitmaps, etc.
Thanks to the reluctance of MS, available documentation rich in SVG is quite limited and I think it is a shame. Many graphical objects in webpages could be represent by a vector representation with the advantage of requiring much less space in servers and requiring less bandwidth. By example, a SVG object (such as an ellipse) with a nice color gradient takes a few hundred of bytes of coding. The size of the code remains practically the same for a tiny ellipse covering a few hundreds of pixels on the screen or the full page, and both of them look beautiful.
Years have passed and maybe finally we'll see a shift in how new web content will be created. SVG is not ideal for everything that is graphics, but definitively it will help to have webpages showing much more efficient graphical content. For once, thanks MS for getting late to the date, at least you got there.