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.
283
comments
.exe to .sh low key turn all windows machines to Linux machines
You're comparing compiled executables to scripts, it's apples and oranges.
I, for one, label my apple crates as oranges.
winebin="wine" if file "$1" | grep 64-bit; then winebin="wine64" fi printf '%s %q $@ || exit $?' "$winebin" "$1" > "$1.sh" chmod +x "$1.sh"
I'm not getting what you are trying to say
You've viewed 283 comments.