Comment Re:Really, about time. (Score 1) 38
The path of least resistance is not SVG. It's a very promising standard, and programs like Inkscape have done wonders with it (and so has KDE), but in browser-land there are simpler solutions that are more widely supported.
So are you trying to say that it's easier to get IE to implement canvas? Or are you trying to say that it's not worth implementing the rest of SVG in the browsers that support it?
Yes, SVG needs to be in tools that target graphics designers, like Illustrator and Inkscape. And I guess, by your logic, those apps need to support canvas too.
Canvas is a simple API for drawing to a space on a web page. That definitely fills some needs. SVG fills some needs too. There is overlap. There's also overlap between plain text and html, nobody's saying we should get rid of one in favour of the other.
As for the size of the spec, that happens as a specification matures. Have you looked at the size of html5? SVG provides a lot of features, there are some common subsets that can be relied on today across numerous platforms. It would be nice if every implementation had all the features, but we can say the same thing about CSS or any number of other standards. Like an alpha channel in PNGs...