I don't think this goes far enough! Make the actually app store be the same file itself. so it's a living application and the file is constantly updated to how you use it. Copy it around, and you carry your data wiht you as well. Let's go deeper. it's a webserver app + the server code + application code + db, so pocketbase++ where it's also the deployment target. Then combine it with APE liek system, and the same fil…
Executable Is a SQLite Database
81–90 of 116 posts
Re: Executable Is a SQLite Database
#82A lot of kernel filesystem features should be inside a database as well.
Yes. In this interview Michael Stonebreaker, one of the original developers of PostgreSQL, discusses (among other topics) replacing the file system with a database : https://www.youtube.com/watch?v=YPObBOwIrHk
Re: Executable Is a SQLite Database
#83ha ha ha
yes
Re: Executable Is a SQLite Database
#84(author) I'm enjoying the comments. When I published a short-paper with this idea in academic circles, the feedback wasn't so kind
Re: Executable Is a SQLite Database
#85Re: Executable Is a SQLite Database
#86> Surprisingly a lot more falls out as well: .dynstr is gone, because name is TEXT and SQLite already interns strings
What's with this claim? SQLite does not intern strings, as far as I can find anywhere, and a quick test shows that duplicate strings are actually duplicated in a database file. You can intern strings in SQLite manually with an intern string table, but it doesn't happen automatically.
Re: Executable Is a SQLite Database
#87Earlier quoted context omitted.
Yes. In this interview Michael Stonebreaker, one of the original developers of PostgreSQL, discusses (among other topics) replacing the file system with a database : https://www.youtube.com/watch?v=YPObBOwIrHk
This is one of those perennial ideas; let's get rid of hierarchical file systems and just keep all the files in a database. Speaking as a user who knows how to keep things organized, I like hierarchical file systems. Store the data in a database if you like, but don't break my metaphor.
Re: Executable Is a SQLite Database
#88One nit-pick;
> The preload table is a list of objects to map last, so their exports win.
made it sound like the 'map last' is a consequence of this new perspective, but it’s really still a loader convention: by definition, the symbol-resolution query needs to give entries in the preload table precedence over ordinary dependencies.
Re: Executable Is a SQLite Database
#89(author) I'm enjoying the comments. When I published a short-paper with this idea in academic circles, the feedback wasn't so kind
Curious what that feedback was, specifically?
I enjoyed all the papers I read on my graduate classes that bordered on "art" whereas now they seem to be obsessed with performance only.
Re: Executable Is a SQLite Database
#90I think this is awesome though, feels like a lot of things on OS's could just be represented by databases - where does it end?