if you could pick a standard format for a purpose what would it be and why?

e.g. flac for lossless audio because...

(yes you can add new categories)

summary:

  1. photos .jxl
  2. open domain image data .exr
  3. videos .av1
  4. lossless audio .flac
  5. lossy audio .opus
  6. subtitles srt/ass
  7. fonts .otf
  8. container mkv (doesnt contain .jxl)
  9. plain text utf-8 (many also say markup but disagree on the implementation)
  10. documents .odt
  11. archive files (this one is causing a bloodbath so i picked randomly) .tar.zst
  12. configuration files toml
  13. typesetting typst
  14. interchange format .ora
  15. models .gltf / .glb
  16. daw session files .dawproject
  17. otdr measurement results .xml
you are viewing a single comment's thread
view the rest of the comments
[–] 14 points 3 years ago* (9 children)

Even more simpler, I'd really like if we could just unify whether or not $ is needed for variables, and pick # or // for comments. I'm sick of breaking my brain when I flip between languages because of these stupid nuance inconsistencies.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 5 points 3 years ago* (last edited 3 years ago) (7 children)

    Don't forget ; is a comment in assembly.

    For extra fun, did you know // wasn't standardized until C99? Comments in K&R C are all /* */. Possibly the most tedious commending format ever devised.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 4 points 3 years ago (5 children)

    ; is also used by LISP.

    And there's REM in BASIC.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 3 points 3 years ago* (last edited 3 years ago) (4 children)

    Batch files also use REM. Or ::. Each of which causes syntax errors in completely different scenarios.

    M4 says it uses #, but that's an echo, and dnl is for real comments.

    CSS still forces K&R style, but on reflection, that's nothing compared to HTML's ⋖!-- --> nonsense. (Edit: or Lemmy's idiotic erasure of HTML-like blocks. If they're not allowed... show them as text, fools.)

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 3 years ago (3 children)

    Fortran uses ! or C in the appropriate column.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 3 years ago (2 children)

    in the appropriate column.

    Alright that's just hideous.

    Forth uses \, and can do block comments with ( and ), except ) is optional in interpreted mode.

    Algol 60 used ¢. ¢ isn't even in ASCII, so god knows how that "your two cents" joke ever happened. How can a language this boring still exemplify how all programmers are dorks?

    Visual Basic uses ' because go fuck yourself. QBASIC origins or not, I don't know how this shipped without at least one meeting where somebody got stabbed. Even the Systems Hungarian heretics should have recoiled in horror.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 3 years ago* (1 child)

    Algol 60 used ¢. ¢ isn’t even in ASCII,

    APL uses "⍝", which isn't even in any human language and was introduced specifically so that APL can have comments.

    https://www.compart.com/en/unicode/U+235D

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 3 years ago*

    /* */ is used in CSS as well, I think.

    Also we've got VB (and probably BASIC) out there using ' because why not lol

    [EDIT] I stand corrected by another comment REM is what BASIC uses. DOS batch files use that, too. They're old though, maybe we give them a pass "it's okay grampa, let's get you back to the museum" 🤣 (disclaimer: I am also old, don't worry)

  • source
  • parent
  • [–] 2 points 3 years ago

    It does not work like that. $ is required in shell languages because they have quoteless strings and need to be super concise when calling commands. # and // are valid identifiers in many languages and all of them are well beyond the point of no return. My suggestion is to make use of your editor's "turn this line into line comment" function and stop remembering them by yourself.

  • source
  • parent