specification VS brain

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/

Brainfuck's super simple to implement, and you can apparently create higher-level languages that compile to it, so arguably it could maybe be useful as an especially unreadable intermediate format for another language.

Then perhaps I could introduce you to a Rust-inspired language that compiles to Brainfuck code. The pinnacle of code elegance.