3 ms·
In canvas's defense, canvas and SVG/VML are different tools for different jobs. For a charting library, you should absolutely use SVG/VML instead of canvas. Yo
by jbail 16y ago
In canvas's defense, canvas and SVG/VML are different tools for different jobs.
For a charting library, you should absolutely use SVG/VML instead of canvas. You don't need the bitmap properties of canvas, canvas doesn't scale well and you can't transform paths like you can with SVG/VML (without redrawing the whole thing).
To do face recognition, bitmap image gymnastics or build an online Photoshop tool, SVG/VML isn't going to cut it though --- you need canvas. Try making a spray paint tool with SVG/VML. Ouch! Using a canvas that's almost trivial.
Good tutorial on using Raphael though. It's a great library.
- pascal-louis 16y agoGreat points, totally agree. Given the hype of HTML5 and canvas, we wanted to make sure to spread the word that it is not the tool that surpasses everything else.
- ergo98 16y agoIn canvas's defense, canvas and SVG/VML are different tools for different jobs. You make good points, however I don't think this entry was particularly negative towards canvas, or merit it needing a defense. However I have to comment on the "different tools for different jobs" bit, as that is a response that comes up in every NoSQL/SQL discussion as well. If you drew a Venn diagram of the optimal uses of SVG and Canvas, just as with NoSQL/SQL, you're going to have a lot of overlap where it's a judgment call. They are different tools that have arguable merits for a lot of the same jobs, which is why it's important to know about both of them.