is svg support really necessary?

I am thinking of removing svg support completely in a future version,

Benefits:

1. smaller library size, because all code related to svg will be removed
2. less testing time, possibly faster development of the library as no svg related code to write or test

Drawbacks:

1. vector graphics mean ability to create resolution independent charts, so I could server render a chart with svg and create high resolution images
2. no server side rendering to svg, server side rendering to canvas is possible with node-canvas though I have never tested it myself
3. when developing new components I usually start with svg as it is easier to develop and troubleshoot, so development might become a little harder initially till we get used to developing with canvas first
4. doing interactive components on canvas is much more difficult, and needs to be explored if it is even possible with the current design

The main motivation behind this thought is that, in order to improve the performance on pan actions, there are some hacks in place for canvas, and these hacks are getting bigger and complex to deal with to support both svg and canvas. I think most users don’t really care if it is svg or canvas, they care about performance and usability.

Thoughts?

[trevorbernard]

Right now I use SVG because over canvas because it’s doesn’t render well on retina screens

[itsjimbo]

https://github.com/Flipboard/react-canvas Just thought I throw this out there… I believe https://cryptowat.ch is built with react-canvas