3 ms·
The benefit of files is that they are a consistent, application-independent abstraction. You can copy, move, rename, backup, version, and generally organize the
by layer8 3y ago
The benefit of files is that they are a consistent, application-independent abstraction. You can copy, move, rename, backup, version, and generally organize them however you want, restrict or grant access, without being constrained by what the respective application supports. Importantly, you can organize files from different applications together without those applications having to know anything about each other. Hyperlinks are no substitute for the object-like, independent nature of files.
Applications that are not based on files create their own little separate universe, or rather island, that isn’t really interoperable.
- dustingetz 3y ago> files are consistent and application-independent I see diverse, inhomogenous state schemas that are deeply coupled to the originating application (internal data structures serialized to disk!) and have arbitrary legacy structural constraints ("document") as well as seams between application silos
- layer8 3y agoYou’re talking about the file contents, not about files as objects. Regarding the file contents, how is that different when the data is proprietarily stored in hidden SaaS databases?
- dustingetz 3y agoI sense a trap, but i'll bite – APIs and schemas and other logical data models can be remixed, at least in principle. Physical data models (i.e. coupled to storage layout) are too low level to be useful, all you can do is load them back into into their originating app.