| ▲ | codingdave 3 days ago | |||||||
A database is a file system when you get down to it. The reason people use them is to abstract up a layer so you can query the data and get the results you want instead of having to iterate through direct reads of a disk, then having to read, parse, and filter what you want from those reads. You could always write code to help do those things direct from disk, but you know what you have just written if you do so? A database! | ||||||||
| ▲ | PaulHoule 3 days ago | parent | next [-] | |||||||
I'd say the filesystem is a database. It would be straightforward, for instance, to implement a lot of the functionality of a filesystem in a database with BLOBs. Random access might be a hassle, but people are getting used to "filesystem-like" systems which are bad at random access like S3. | ||||||||
| ▲ | uticus 3 days ago | parent | prev [-] | |||||||
> You could always write code to help doing those things direct from disk, but you know what you have just written if you do so? A database! Yes, but that's my point. Why is this not a part of the standard library / typical package with very little friction with the rest of the code, instead of a separate program that the standard library / typical packages provide in an attempt to reduce the friction? Or are you making the general point that databases already existed prior to the standard libraries etc, and this is just a case of interfacing with an existing technology instead of rebuilding from scratch? | ||||||||
| ||||||||