• dream_weasel@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    2
    ·
    7 days ago

    Ew no way. Best way to make document structure portable, or to move prose or visuals between contexts. It’s also exceptional if you want to automatically generate documentation with code or services that generate graphics.

    ALSO you can version control it with git which is a good enough reason in and of itself unless you can use markdown for your purposes instead.

      • jcorvera@quokk.au
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 days ago

        I would have to agree with dream_weasel. It’s all about portability. Though, I would like to add on accurate reproducibility. LibreOffice’s font rendering differs from system to system. A typesetting system like roff, TeX, and Typst aims to be reproducible, with TeX being the most as it uses packages and its own font format for rendering. The same argument can be made with MIDI vs Module. While MIDI can be used everywhere, all it is is just note data and metrics. Modules contain all of that plus the sample data, allowing for near perfect reproduction.

      • dream_weasel@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 days ago

        I’m a neovim guy myself, so mostly I’m in markdown. Most of the latex stuff is for document production and it’s easy as keeping a skeleton file with the includes set up on a letter heading. If I have something that NEEDS to be printed and markdown wont do it, I’m definitely using latex not libre. I’m not sure I can even use any kind of writing tool without vim bindings anymore anyway.