Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • It's wonderful to see people trying to fork SQLite in any way possible, to supposedly build a better product with AI, out of smt that's been built by seriously talented people for over 20 years.

    Kudos to the team behind SQLite. These people built smt absolutely amazing!

  • I don't understand why you would want this.
  • Psyched to see this! I've been working on my own similar thing that sucks and I don't want to - I want to write a local first music app that syncs across all my devices. This might get me there!
  • Did I read that correctly that there’s no WAL?
  • Would be good, but why not to vibe code this database myself if I had a problem with my current database?
  • I let agents do their things but I would not trust them with my data without extensive validation. A database efforts main product is not exotic data structures but validation.
  • Why would I trust my data to a vibe coded database, over a battle tested, tested to hell and back one?
  • So the main feature of this project is that it's easy to fork a database, however it's 1.2x to 4x slower than sqlite, and it's level of testing and validation will be nothing like sqlite.

    The simple way to fork a sqlite db is just to copy it, but if that is too slow you could use it with a copy on write filesystem, either something native, a FUSE filesystem, or build a sqlite VFS.

    That would probably be faster to build, faster to run, and easier to validate.

Explore Birbla archives