Comment by jelder
2 years ago
The Slack use case highlighted on the front page would be better if Slack markup was an available syntax. Slack is not really Markdown, so composing messages in Heynote won't have high fidelity.
One thing that often trips me up is that links and code formatting cannot coexist:
[`method_name`](https://github.com/example/example/blob/main/src/foo.rs)
Would be rendered by most Markdown engines as a link with fixed-width text. Do the same thing in Slack and text will be fixed-width, but won't be a link.
There's a partial summary of the differences here: https://www.markdownguide.org/tools/slack/
Not only that. It seems that with all the millions they have, Slack devs were unable to implement the most basic bracket balancing in the link parser.
Try to send a link with a title including square brackets, and contemplate the disaster that gets interpreted from it:
(spoiler: it just thinks that the link title is "Unmarshal(data [" and somehow inserts links into the rest of the words.)
I agree with the use case, but also wonder if it’s more on Slack, Jira, etc., to try harder to adopt Markdown.