Here's why Raphael.js and SVG totally rock.

There's also gRaphael specifically for charting: http://g.raphaeljs.com/

Also, the article mentions that IE doesn't support the tag. While this is true, you only need to add the excanvas JS library to use in IE.

I have found myself using jQuery SVG more. This link shows what other people think of the two:

  http://stackoverflow.com/questions/588718/jquery-svg-vs-raphael

The version of Raphael I used at one point had to be in complete control from object 1 and could not import SVGs. So let's say I generate an SVG via graphviz and then want to make some of the nodes interactive (or at least animate). I get a good amount of tweening via the jQuery interface, including the ability to load up the externally created SVG.

Anyway, for comparison, here is the jQuery SVG interface:

  http://keith-wood.name/svg.html

Why have I used the SVG? It animates smoother in HTML4 on iPhone's Safari and on my linux distro's Firefox than when I tried canvas manipulations.

More recently, I noticed the HTML5 canvas stuff being smooth for both. Still, the benefit of the SVG is having the ability to treat each object as its own DOM element, where you have to rig all that framework yourself for graphical objects you create on the canvas.

I agree - I tried Raphael but actually found it a bit limiting. I can live without IE support (I can use Flex for that) so jQuery SVG looked like the better choice.

The only criticism I could make of jQuery SVG is that the docs often assume that you know a lot about SVG, but that is pretty minor.

I really hope SVG finds its place in the new HTML5 wave. I would hate to see it die