3 ms·
> For me it's about proprietary vs. readable - unless it's obviously necessary for performance I think I'd still prefer 'flat file' to sqlite, but basically I j
by tasuki 4y ago
> For me it's about proprietary vs. readable - unless it's obviously necessary for performance I think I'd still prefer 'flat file' to sqlite, but basically I just want something that isn't an incomprehensible blob, that I can use with other tools etc.
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!
- OJFord 4y agoI 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.)
- MaxBarraclough 4y agoI 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).