4 ms·

Why should Slack support GitHub's implementation of markdown, why shouldn't they just use the common markdown standard?

• scrollaway 9y ago
  Is that really a question? For convenience of course. Also, https://githubengineering.com/a-formal-spec-for-github-markdown/ https://githubengineering.com/a-formal-spec-for-github-markd...
  • unfunco 9y ago
    It's only convenient for users of GitHub, there is surely a large number of users that use both, but there is also a common standard.
    • scrollaway 9y ago
      But you realize that there isn't a common standard, right? Markdown is a language which has no official spec. CommonMark is as close as it gets to one and that one does include github-style code fencing, so I don't know what you're even on about.
      • unfunco 9y ago
        It was CommonMark I was thinking of, it just seemed to make more sense (to me at least) to implement that reference, rather than one that seems specific to GitHub (nothing against GitHub flavoured markdown, I use it and I like it's simplicity)
• DoofusOfDeath 9y ago
  They should support multiple markdown languages, including Github's. The reason is that when using slack with github integration, it's annoying to need to switch markdown language as one goes back and forth between the two. And Slack's lack of support for code formatting, bullet lists, etc. is IMO a sorely missed in that scenario.