• unknowing8343@discuss.tchncs.de
    link
    fedilink
    arrow-up
    30
    arrow-down
    1
    ·
    3 months ago
    • ISO date and time.
    • Metric system.
    • USB-C.
    • Git.
    • ConventionalCommits.
    • Semantic versioning.
    • XDG Base Directory.
    • OpenDocument.
    • HDR10+.

    Also, I would enforce every online shop, transport company, hotels… All of these functioning under a federated market, sort of like the fediverse. Impossible to corrupt. Impossible to monopolize. True choice.

    • lud@lemm.ee
      link
      fedilink
      arrow-up
      20
      ·
      3 months ago

      Impossible to corrupt. Impossible to monopolize

      You would be surprised.

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

      Semantic versioning.

      Most of the time. I use calendar versioning (calver) for my internal application releases because I work in IT. When the release happens is more consequential than breaking changes. And because it’s IT, changes that break something somewhere are incredibly frequent, so we would constantly be releasing “major” versions that aren’t really major versions at all.

      OpenDocument.

      Agreed compared to .doc and .docx. And if you’re going to version control it, markdown instead of a binary blob.

      For academic documents in STEM fields, I’d love to see a transition from LaTeX to Typst. Much cleaner, better error handling, and it has a web UI if people don’t want to install a massive runtime on their own computer.

      • tmpod@lemmy.ptM
        link
        fedilink
        arrow-up
        1
        ·
        3 months ago

        Yeah, Typist is great and has potential for much more still! The big issue is something like the network effect, LaTeX has everything you could possibly want, pretty much, and people will continue to primarily support it because it’s the biggest tool. It will be hard to break that cycle, but in the long run it may be possible.