3 ms·
Wondering how you feel about that? Was all the extra effort worth it in the end? Considering you only support a single browser anyway. Imagine a similar effort
by iamleppert 10y ago
Wondering how you feel about that? Was all the extra effort worth it in the end? Considering you only support a single browser anyway. Imagine a similar effort per browser. There's even a lot of variance between Chrome, latest FF, IE Edge, etc.
In my case I wasn't even manipulating the actual SVG nodes, just using transform CSS operations on them (transform and transfrom3d).
- aidos 10y agoThe final result is really nice. The user experience is smooth, and that's what matters most. I'm not convinced that using canvas would have saved me that much effort. You just don't know what's going to bite you until you start building with these things. One of the nice things with svg is that I can work with it everywhere. In the browser, on the backend, I can even manually manipulate it in my text editor. Fortunately I've opted to constrain myself to chrome. If I had to support all the browsers that would have been the thing that ate up all the time (irrespective of whether it was canvas or svg). Anyway. Sounds like you've also experienced the complexities enough to understand that once you push things a bit harder than usual you need to do extra work to make things play nice :) At the end of the day, I'm happy with the result. Besides, for all the trouble it's nowhere near as complex as other bits of our system!