We started on a new project Friday and decided to go with Raphael. I'm amazed at what it can do - awesome stuff. Why on earth would you decide to write your own cross browser (vml + svg) library when it's already been done and the result is already very good?
But SVG isn't supported in any version of IE... For me, that's the main reason to use Raphaël.
It’s supported in IE9+, and for earlier versions (if necessary) there’s SVG Web or Chrome Frame.
So your project just fails on IE7 and IE8?
Different projects obviously have different needs. I’m just pointing out that much of what I’ve heard people say about Raphaël is along the lines of “it’s nicer to use than raw SVG”, and providing a contrary data point.
Often, when trying to figure out what technology stack to use, developers look around at what seems to have chatter and hype. I think that in some cases they’d be better served by just learning the lower-level API, which isn’t too hard.
You didn't answer the question.
If he uses plain SVG, and IE7/8 doesn't support SVG, ________________.
To be honest though, I found that in trying to build anything more complex or with much user interaction, just working directly with SVG APIs and building up my own abstractions as necessary was easier and much more flexible. People shouldn’t be afraid to learn SVG: it’s pretty easy!
For anything driven by data, I recommend looking at D3, which is designed around some very powerful ideas.