Re:Smaller is better – The rise, fall, and rise of flat file...
by OJFord on Sunday May 22, 2022 @03:52PM
(#31472047)
I was not aware I gave a definition for it. I didn't mean it as an antonym for 'readable', if that's what you mean.
Plaintext could be in a proprietary format but that's far better than proprietary compressed database that's a job to work out what even made it (if that wasn't proprietary itself!). Proprietary plaintext might even be better than open standard blobby format, depending on what you want to do with it. (Better for git and backup, worse for opening in competitor tools.)
Re:Smaller is better – The rise, fall, and rise of flat file...
by MaxBarraclough on Monday May 23, 2022 @03:23PM
(#31483771)
I think their point was that proprietary is not a synonym for bespoke.
If your code is Free and Open Source, then its file-format is presumably not proprietary, whether or not it makes use of an existing standard format (like JSON) or solution (like SQLite).
That is not exactly what proprietary means. Though I feel the same - plain text can be versioned and managed by various tools and that is great!