Single post
jump to replies
Why I prefer human-readable file formats
When I say human-readable file format, I'm referring to text-based files that can be opened, read, and understood without the need for any specific software or proprietary interface. They include formats like Markdown, JSON, YAML, INI, TOML, CSV/TSV and even fixed-width text files where the content and its structure are visible, transparent, and editable in a simple text editor [...]
https://adele.pages.casa/md/blog/why-I-prefer-human-readable-file-formats.md
3 replies
back to top
@adele the generality of the text editor (and unix text processing tools) is very nice, and when working within the current ecosystem i always choose them.
and yet i also find text formats harmful. the vast majority of programming languages, config files, and exchange formats reinforce english-supremacy. different people have different layout preferences - spacing habits, column widths, indentation styles, and in programming naming conventions - why must they compromise on those to collaborate? and those compromises inevitably favor the parties with more power.
so i am intrigued by the possibility of general self-describing binary formats that do not embed privileged perspectives. i suspect a similarly general ecosystem of tools could be built around something with more structure than text (which is, after all, also a binary format), and perhaps be even better.
@tryst interesting perspectives. But, I don't see which file format could solve this dilemma
@tryst maybe choose to use #Esperanto ;-)