Re:The BeOS file system, an OS geek retrospective (2018)
by kitotik on Sunday September 20, 2020 @02:46PM
(#24536267)
Tying your app to the fs isn’t that bad if the fs is flexible and portable enough such as zfs having the ability to use plain files.
Doesn’t seem much worse than tying it to a particular database or API
Re:The BeOS file system, an OS geek retrospective (2018)
by em-bee on Sunday September 20, 2020 @11:35PM
(#24539541)
my first response was 'but filesystems live on the disk' while databases are simply to set up in userspace. but then i realized that with FUSE and filesystem-image files and the right tooling the same flexibility can be achieved, and also, on the other side high performant databases want to live on the raw disk to be in full control of the write process to disk.
what remains is that the difference between a filesystem and a database is the API used to talk to it.
I imagine the extended attrs and db would be amazing for app devs, but probably wouldn't see much use in the real world because it ties your application to the file system. But what else?