specification VS svgomg

TinyVG follows the similar goals: an alternative to SVG with a specification which trades off features for simplicity. https://tinyvg.tech/

I wholehearedly agree with your point on information blackholes but I think the reason some people hate SVG is that they've had had to advanced things with or had to work with the spec and implement something around it. I haven't done so myself but I can tell pain when I read it.

Here is a mostly compatible alternative: https://tinyvg.tech/

I created a library to parse TinyVG files

After taking an interest in TinyVG I got to wondering if there is a similar idea just applied to conforming SVG files. Basically a format that includes nothing but basic paths, colors, gradients and a few shapes to make the implementation relatively easy to create.

If so, can you please make an issue in the specification repo: https://github.com/TinyVG/specification/

Im assuming if you click on the red dot you get to see the names. Try to get a svg without the names. Get it through SVGOMG https://jakearchibald.github.io/svgomg/ and then make a component out of it. Add click listener to the dots and voila

SVG Optimizer

SVGOMG for optimizing SVG

Use https://jakearchibald.github.io/svgomg/ to strip out all the unnecessary data.

I came here to say the same thing.

Somebody recently pointed me at a nice online GUI for svgo, so you can try it for yourself without installing anything: https://jakearchibald.github.io/svgomg/

Use what ever you to create it the run it through https://jakearchibald.github.io/svgomg/

In addition to the good points others have posted, you could also try using the SVGOMG tool to reduce the final size.