I've played with roll-your-own-markup myself, borrowing from various wiki markup notations. In this LinkyIO demo, I don't like how it turns URL's and emails int

I've played with roll-your-own-markup myself, borrowing from various wiki markup notations. In this LinkyIO demo, I don't like how it turns URL's and emails into buttons. Usually you want them as hyperlinks by default. They probably have ways to adjust the behavior, but that of course complicates the syntax. Generally the best approach depends on the intended use, because you make the simplest or smallest commands or defaults for the conventions most commonly used in that domain context, and add more commands or parameters to adjust for the non-common needs. But in a different context, what's common is often different such that your short-cuts and defaults are mistuned. Frequency-of-use is important to syntax/markup/language design, yet varies per domain. You can make the language more "meta" such that you can define your own shortcuts and defaults, but then your language has a bigger learning curve. In short, one size can't fit all.