xyheme
Joined 6 years ago
Karma
76
Submissions
66
Member since
Jun 21
https://xieyuheng.com
View on Hacker NewsRecent submissions
Comment · 3 years ago
directory tree is not as easy to view and edit as JSON.
One big JSON file is harder.
I am not fancy, and the aim is to simply use file system as database.
Not fancy stuff like "database as file system as database".
Comment · 3 years ago
Me and a lot of linux user friends are using btrfs.
Comment · 3 years ago
I should thought about that.
Comment · 3 years ago
Isn't WinFS the reverse of "file system as database"?
Which is "database as file system".
Comment · 3 years ago
That all can be achieved by using file system as database.
Not even complicated to implement.
See couchDB for how to handle "what if two people are editing a file at once".
Comment · 3 years ago
JSON is there for human to read a record of data by group.
I think it is only good to use directory as data table to store JSON data files, but not for JSON data properties.
Comment · 3 years ago
Inode limits depends on the file system you use.
I am using Btrfs.
Btrfs inode limits is in a whole different league (whereas ext4's inodes are allocated at filesystem creation time and cannot be resized after creation, typically at 1-2 million, with a hard limit of 4 billion, btrfs's inodes are dynamically allocated as needed, and the hard limit is 2^64, around 18.4 quintillion.
> -- https://unix.stackexchange.com/questions/18388/what-are-the-...
Comment · 3 years ago
> The main reason is that I can use a variety of tools to view and manipulate files.
This is also the reason I am researching this old "What if" problem.
Because I think comparing to some version of MySQL or PostgreSQL, files are stable, open and timeless.
Comment · 3 years ago
Thanks for the reminder about meaningful pathnames :)