Whether you’re really passionate about RPC, MQTT, Matrix or Nostr, tell us more about the protocols or open standards you have strong opinions on!

    • TechNom (nobody)@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      ·
      7 months ago

      Commonmark leaves some stuff like tables unspecified. That creates the need for another layer like GFM or mistletoe. Standardization is not a strong point for markdown.

      • Dessalines@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        7 months ago

        I believe commonmark tries to specify a minimum baseline spec, and doesn’t try to to expand beyond that. It can be frustrating bc we’d like to see tables, superscripts, spoilers, and other things standardized, but I can see why they’d want to keep things minimal.

        • TechNom (nobody)@programming.dev
          link
          fedilink
          English
          arrow-up
          0
          ·
          7 months ago

          Asciidoc is a good example of why everything should be standardized. While markdown has multiple implementations, any document is tied to just one implementation. Asciidoc has just one implementation. But when the standard is ready, you should be able to switch implementations seamlessly.

    • xigoi@lemmy.sdf.org
      link
      fedilink
      arrow-up
      0
      ·
      7 months ago

      Have you read the CommonMark specification? It’s very complex for a language tha’t supposed to be lightweight.

      • frezik@midwest.social
        link
        fedilink
        arrow-up
        0
        ·
        7 months ago

        What’s the alternative? We either have everything specified well, or we’ll have a million slightly incompatible implementations. I’ll take the big specification. At least it’s not HTML5.

        • xigoi@lemmy.sdf.org
          link
          fedilink
          arrow-up
          0
          ·
          7 months ago

          An alternative would be a language with a simpler syntax. Something like XML, but less verbose.

          • frezik@midwest.social
            link
            fedilink
            arrow-up
            0
            ·
            7 months ago

            And then we’ll be back to a hundred slightly incompatible versions. You need detailed specifications to avoid that. Why not stick to markdown?