if you could standardise a file format for a specific task what would you pick and why
if you could standardise a file format for a specific task what would you pick and why
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:
- photos .jxl
- open domain image data .exr
- videos .av1
- lossless audio .flac
- lossy audio .opus
- subtitles srt/ass
- fonts .otf
- container mkv (doesnt contain .jxl)
- plain text utf-8 (many also say markup but disagree on the implementation)
- documents .odt
- archive files (this one is causing a bloodbath so i picked randomly) .tar.zst
- configuration files toml
- typesetting typst
- interchange format .ora
- models .gltf / .glb
- daw session files .dawproject
- otdr measurement results .xml
You're viewing a single thread.
Markdown for all rich text that doesn't need super fancy shit like latex
which markdown implementation tho ?
GitLab/Hub obviously. Also it doesn't matter since I don't need to compile it to read it.
Oh I'm not brave enough for politics.
You compile your markdown and don't read it raw? /s
unironically a good point tho.
I'd argue asciidoc is better, but less well known
asciidoc lost me because it's not a markdown superset. Why invent yet another way of marking headlines?
Also GitLab/Hub markdown is the standard and I don't think we need another.
That's a weird way of thinking. I could make the reverse argument.
Markdown lost me because it's not a subset to asciidoc, why invent yet another way of marking headlines?
Also asciidoc is the standard and I don't think we need another.
This whole thread is discussing ideal standards.