• friend_of_satan@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    3 months ago

    I migrated from mediawiki to markdown in git 8 years ago and never looked back. The ability to publish to any number of static site hosts, and use any number of editors, some that have preview mode, is rad. Data liberty, data portability, wide support, easy to convert, easy to grep, good enough for 95% of written notes.

    My biggest gripe is poor support for tables of data.

  • Sundray@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 months ago

    Interesting stuff, but my main takeaway is that very little of my output is worth keeping! (Who’s going to need out-of-context Star Trek shitposts in 20 years?)

  • addie@feddit.uk
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    Man alive, all that time I wasted learning LaTeX in that case. Supports tables properly, “floats” pictures and figures about without messing up the flow of text, exceptional support for equations, beautiful printed output…

    Suffers from a completely insane macro-writing language, and its markup is more intrusive in the text than markdown’s is. Also, if you have very specific formatting output requirements (for a receiving publication, for instance) then it can be somewhat painful to whip into shape. Plain-text gang forever, though.

    • dreugeworst@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      3 months ago

      haaave you heard about our lord and saviour Typst?

      same layout algorithm as LaTeX, but:

      • simpler markup
      • sane, consistent scripting language
      • fast compilation, including incremental updates so you can have a process watching your file and instantly create a new PDF on changes
      • easy collaborative editing through their web app
      • actually understandable error messages