@robpike I would rather maintain that it has been a degradation from the persistent objects which several contemporary systems could use.

Neither did they silo you into solely using them with a particular program though.

But the unix model of #filesystem #storage has been a nightmare for #metadata, and non-transactional filesystems in general for #DataConsistency & #integrity.

A #PersistentObject #database served by a #capability broker would be far superior for security and data management.

@mia @chjara Of course none of those filesystems provide any sort of #DataConsistency guarantees, they solely provide #DataIntegrity. That means any write that doesn't fit within a low-level transaction (in btrfs and maybe zfs) as well as all streaming writes done by a program are at risk of data corruption should the program crash or the power go out.

Any concerns of consistency have to be handled in software, such as a #database. Which basically no one does (for desktop programs, anyway). :/