Better and cleaner compared to what? What does this improve on? What pain points does it solve?
Also I commented with some feedback in another part of this post.
Interesting. Ambitious, but interesting. MD does have some serious warts.
It would be nice if you could provide a shorter summary of the differences, mainly the pain points it solves and how it solves it.
A few notes so far:
* Markdown has [named link references] that clean up inline links a lot. I didn't know about them until recently.
* How do you specify the language for code blocks so they can be syntax highlighted? That seems like a missing feature, and one I won't be able to work without.
* I agree that header delims in Markdown seem literally backwards. ### seems like a more primary header than ## or #, and === more than --- when under the text.
* I also agree that h4-6 are useless, but I would need h3 at least.
This project is interesting, and I'd like to see it gain traction, at least in discussions. I started a similar experimental language in 90s.dev for similar reasons.
[named link references]: https://github.com/sdegutis/90s.dev/compare/6d83a384e5aec81c...
I really dislike this for headers, but also, this marker is only valid inside code blocks and is optional.
> How do you specify the language for code blocks so they can be syntax highlighted?
See above, with ###Go and then add Prism.js into your document.