Thank you for the kind words and for reporting the bug. I agree that providing a simpler, cleaner alternative is essential, and I'm working hard to make it just that. Regarding the bug, I'm already looking into fixing it to ensure it doesn't happen again.
This is correct, the idea is that you can type things like "6 foot 3 inches" and have it evaluate as an addition. But the example shown above is definitely a problem, I'll try to think of a work around.
I'd think that rule only makes sense after a symbol representing a unit (including potentially 6'3"). Certainly <number> <named constant> should logically assume multiplication.
The core features are pretty much universal and used in a lot of apps (chats, forums, git repositories, project management). Custom flavors maybe not rendered correctly at times but this doesn't make documents unreadable
The core features used in a lot of apps include different flavors, like GitHub Markdown and others. The closest thing you have to a unified Markdown is CommonMark and even that is forked for GFM. Yes, headers, bold and italics text, and lists are nice but there is a lot more to take into account when you are trying to supplement docs that other extensions add.
There are plenty of great OSS that looks great but they are often backed or owned by a real company and not just a community project. Gitlab, Firefox, VLC, Blender, VScode or BBB, Jitsi Meet for videoconference...
Most of the projects you listed, aren't developed in the `Bazaar` environment. They have a complete team with managers, designers and developers working full time in cohesion. They are cathedrals, who open sourced the product.
They explicitly said it will be maintained but they will not be any new features. It's not the same as a project with no commit for three years...
I think this post is a bit over the top and shouldn't be required but, I agree, clear communication in OSS librairies is important.