a few things against a plaintext version:
- people can’t actually edit the text in a computer editor-- there is no syntax checking, so when the files import there will inevitably be typos and it’ll just fail, without any warnings, which is a completely terrible system-- hence useless
- manual editing means files get saved by various editors/os’s with different LF tactics, hence the parser breaks (granted, this just means the parser needs to be smarter-- currently it is not-- if you edit these files with a noncompliant editor (not sure which works) you’ll simply basically corrupt the file.
a js scene-to-text converter would be very lightweight and would live online, no dependencies needed.
so, what’s worth examining are what are the advantages to plaintext storage? yes, it’s human readable, but the only time you’ll ever care about that is to either 1. see what the file is while sorting your usb disk or 2. copy-paste the text to a forum post.
the forum post will be unformatted, but looks ok in a codeblock. if we repair the linefeed issues someone could copy-paste it back into a file on disk. but otherwise it’d be smarter to just attach the source file to the thread.
perhaps the reason i’m pushing for something like msgpack is that it can set up a sensible framework for saving preset data for other things, ie, kria presets, which absolutely need no plaintext, and have have values that are not 8 bit (hence would need more characters and manual typecasting) or arrays which would be better handled with a library.
ie, the pattern read/write code is super clunky as is with plaintext, where with a serializer it’d quite possibly be one line of code.
i know it seems like i’m pushing hard on this, but i absolutely can be swayed, please don’t take what i’m saying as what should happen!