|
@stdlib | |||||
|
VMS basically got this right IIRC; rather than thinking of files as blobs, it treated them as objects that were just tables. a text file was "just" a set of rows that a text editor contiguously visualized, like Excel. two people could trivially read/edit files concurrently, etc
|
||||||
|
||||||
|
Reid D. M.
@arrdem
|
1. velj |
|
Databases fucking suck send tweet
|
||
|
|
||
|
Reid D. M.
@arrdem
|
1. velj |
|
"put the thing in a database" great now it has no version history, lives on a server somewhere which could fail, and requires special tools to access.
|
||
|
|
||
|
Reid D. M.
@arrdem
|
1. velj |
|
anyway text data formats are fine, and you can make them better.
|
||
|
|
||
|
Chadwick Blazington
@stdlib
|
1. velj |
|
filesystems suck complete ass, though, even more-so than most databases.
|
||
|
|
||
|
Reid D. M.
@arrdem
|
1. velj |
|
yes, but consider single files
|
||
|
|
||
|
Chadwick Blazington
@stdlib
|
1. velj |
|
i don't think that's much better, because you're almost always stuck with POSIX as a common denominator anyway (which sucks) so you're still at the mercy of the fs layer. e.g. how to safely rename files with fsync is unspecified.
|
||
|
|
||
|
Chadwick Blazington
@stdlib
|
1. velj |
|
by then you might as well say fuck it and upgrade your filesystem and interface with it directly through non-standard means. you'll immediately want transactions for safety, but now you're just using "flat" namespaces as your tables. it *is* a database at that point
|
||
|
|
||