4 ms·
There's more to plaintext than .txt files. I'm building an app (3D memory palace) and the save file format is JSON. It's not plaintext, but it is text, and str
by meesterdude 5y ago
There's more to plaintext than .txt files.
I'm building an app (3D memory palace) and the save file format is JSON. It's not plaintext, but it is text, and structured in such a way that you could rebuild the app yourself if you wanted to - or still have access to your data should the app stop working one day. It also means it's trivial to edit the JSON if you want to add or remove something, or make mass-changes that would be impractical to do within the app itself.
At work as a web developer, I'll often facilitate CSV import & Export for Product to work with the app. This lets them use Excel, which they're already comfortable with, and removes me from the development cycle because now changes are just a file upload that they can do themselves.
Both JSON and CSV are great plaintext ways to represent structured data. Personally, I wish there was a markdown for excel, or some way of representing the entire capabilities (such as formulas) in plaintext instead of in a proprietary XLS. Hopefully someone has something in the works around that.
Proprietary is easy - just do whatever you want. But doing things in a way that lets users & other developers "yes and" your work is an under appreciated value add.
- npteljes 5y agoI think this is a fantastic attitude. And if the file grows too big, you can also do a simple compression. MS office is a weird thing in this regard. The current formats are technically open (called Office Open XML), but good luck with the multi-thousand page reference.