This is the database that shows up when I’m trying to pitch PostgreSQL, but the boss read a blog post and now has Strong Opinions, and now my job depends on writing a comparative analysis of PostgreSQL and TabDB that reaches the right conclusion while also making anybody who advocated TabDB look smart and feel like they contributed. I literally just wanted to code.
This is a good idea but badly implemented, there is no persistence between browser sessions. Clearly they should be using the document.location.hash to store the compressed db then you also get undo via back...
Also with no LLM or chat based ui it's a hard pass from me.
It's a cool project but I wouldn't use a blockchain for this. Federation is the new hotness, and it's way better, for reasons. So yes, I won't use this until they allow me to federate my browser tabs.
You just need it to send an email on every update with the full db contents and then set up another browser elsewhere to read the emails and update their tabs and you'll have state of the art federated database replication.
I’m can’t believe that nobody said this but I can’t run this bare metal on my raspberry pi pico. It not being a single header C89 with no dependencies to the stdlib makes it a hard pass for me
I call this fake news, browsers have had the ability to scale vertically and horizontally for ages and obviously TDB fully supports it as well. It even boasts experimental support for multi monitor setup (although some glitches are to be expected)
but let's not get off topic, so let's instead explore how both tools could work together.
first of all, tabfs is going to map the tabdb to files and directories in the filesystem. (btw: that would be an interesting tool in itself. storing rows and columns as a directory tree, which each field being a file...)
Is it actually possible to allow a tab/site store and manage large persistent datastore? It would be useful to build certain applications that way (like some next gen desktop apps).
I wonder how the first browser was made. I mean obviously the developer would have needed an existing browser to run it in, not to mention a browser to run their ide, their debugger, the container orchestration. Seems impossible. Maybe they had to use slack bots or something.
> Every time you run an SQL query, it grabs all the data stored in the neighboring tabs' titles, concatenates it, unzips it, and loads it into an in-memory sqlite database
Last time I checked, Firefox stored bookmarks in a SQLite db as well.
This is my favorite kind of small fun projects, reminds me of the video about harder drives [1], where the author used ICMP echo requests to store data
Hmm maybe I’m not being fair but my initial reaction is that this uses SQL.js as a database and browser tabs for backups. And then restores from the backups before each query instead of just reading from the in-memory db.
Can this be connected to a 3D printer and create 3D fractal objects that are a physical representation of the database that can then be laser scanned to read the data?
