I always found SVG a non-readable file for most images I’ve used. Yes, if you place a simple rectangle it works, but when you export an image it’s almost impossible to edit it manually.
I like this edge on TVG, as a binary format is more optimal for size and you’re not losing much visibility on this case.
I believe TVG popularity will depend on the final use cases. Having to use a poly fill on the browser delays the reproduction of the image until JS is loaded. It would be interesting to compare both cases: download an optimized SVG vs download and print a TVG file using the polyfill.
oh yeah i don't edit paths by hand, just stuff like cleaning up groups, removing unused css, changing colors, etc. when i do need to edit paths i use https://yqnn.github.io/svg-path-editor/
Comments
I always found SVG a non-readable file for most images I’ve used. Yes, if you place a simple rectangle it works, but when you export an image it’s almost impossible to edit it manually.
I like this edge on TVG, as a binary format is more optimal for size and you’re not losing much visibility on this case.
I believe TVG popularity will depend on the final use cases. Having to use a poly fill on the browser delays the reproduction of the image until JS is loaded. It would be interesting to compare both cases: download an optimized SVG vs download and print a TVG file using the polyfill.
idk i export SVGs from inkscape and edit them by hand pretty frequently, it's not that hard.
For me most changes are related to colors and text. Paths are quite difficult to edit.
oh yeah i don't edit paths by hand, just stuff like cleaning up groups, removing unused css, changing colors, etc. when i do need to edit paths i use https://yqnn.github.io/svg-path-editor/