Rendered at 11:25:21 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
vrighter 5 hours ago [-]
Why would I trust my data to a vibe coded database, over a battle tested, tested to hell and back one?
dekelpilli 5 hours ago [-]
Dolt has been around for 7 years[0]. Doltlite, like most software nowadays, has been touched by LLMs, but dismissing this project as "vibe coded" seems harsh
> Gas Town is for “write-only code”, … If you adopt Gas Town, you will lose the speed benefit of multiple agents if you read the code it produces. The first time you stare at an 8,500 line Git diff and try and parse what happened, you’ve lost. Go back to a single Claude Code session. Gas Town isn’t for you.
So none of the code has even been read by the author, it’s purposely overly verbose. “Touched by LLMs” seems to downplay just how vibe coded this is. I won’t use this database for anything.
Skinney 5 hours ago [-]
> Doltlite, like most software nowadays, has been touched by LLMs, but dismissing this project as "vibe coded" seems harsh
From the article, at the end of the second paragraph:
> Could a team of agents pull it off? It only took about 2,000 pull requests but DoltLite going Beta proves a team of agents certainly could.
The first PR was merged March 17th.
"vibe coded" seems pretty fitting
solarkraft 3 hours ago [-]
If going through a strongly designed process with quality gates is vibe coding, I guess so. I thought the term was reserved fir “claude, make this happen” style development and the term for the more professional approach was “agentic development”, though this seems to be another layer higher.
Grouping it all under “vibe coded” loses precision. Sure, it uses AI, but differently from other projects and with different implications.
louis-lau 14 minutes ago [-]
Agentic development still requires human review and human ownership of PRs. This is vibe coded. Seems precise to me.
rurban 1 hours ago [-]
Battle tested and tested to hell, maybe yes. But still horrible insecure architecture, with read-only access being able to write. And totally insecure full text search. https://github.com/rurban/hardsqlite
throw234259 3 hours ago [-]
Look at dev process (i did), this think is "tested to hell" and "battle tested".
But the feedback loop was automated and accelerated. Instead of 1000 loops spread over 20 years, it had 1000 loops over a few months.
Calling it "vibe coded" just shows something about you, not the project. It is not production ready yet, but that is not for fast ai dev or for technical reasons. It needs independent reviews, independent verification, and reputation.
postexitus 2 hours ago [-]
This, from a 1 day old throwaway account, tells a lot.
vrighter 2 hours ago [-]
I don't trust AI testing. An automated loop == zero testing in my book.
grebc 3 hours ago [-]
Battle tested means deployed in production.
So when you say battle tested earlier, and then not production ready later - which one is it?
esperent 2 hours ago [-]
That's selling it short. You could deploy something to production in minutes. Battle tested implies it's been not only deployed, but heavily used in all kinds of scenarios, and in the case of sqlite, probably by millions of different apps.
But anyway I assume that random name green account above is just a pro-vibe coding bot.
grebc 1 hours ago [-]
It’s ridiculous how common the bots are becoming, then again Sam’s put a lot of money on the line so can’t be having bad vibes.
3 hours ago [-]
WatchDog 6 hours ago [-]
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.
ncruces 3 hours ago [-]
It's easy to do a VFS that handles instant forking (snapshots).
The problem DoltLite solves is merging, not forking.
IanCal 5 hours ago [-]
> however it's 1.2x to 4x slower than sqlite
No? Where are you getting those figures? It feels like you may have pulled that from the 125 and 400 us numbers?
> 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 wouldn’t really solve what dolt does though.
> and it's level of testing and validation will be nothing like sqlite.
They’re using the other dolt tests as well as the SQLite tests. Nothing will hit the level of real world testing SQLite does.
God that had a lot of llm'isms. Couldnt get through it with all the repeats and info bloat.
oreally 29 minutes ago [-]
I'm a little more interested how they automated the process to such a degree. How do they do it? Subagents?
SipitenoMK 5 hours ago [-]
Would be good, but why not to vibe code this database myself if I had a problem with my current database?
solarkraft 3 hours ago [-]
You’d have to do the relevant R&D and maintain the product.
Sharlin 3 hours ago [-]
"But Claude does that for me"
nylonstrung 2 hours ago [-]
Everything touching this ecosystem (Gas Town, Dolt, Beads) seems like the absolute nadir of vibecoded slop
This specific community has been a Schelling point for some of the worst engineering practices I've ever seen and a desire to abstract away all details of code to LLM personas like the "Refinery" and "Deacon"
vonnieda 5 hours ago [-]
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!
grebc 7 hours ago [-]
Did I read that correctly that there’s no WAL?
anon291 7 hours ago [-]
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.
Joel_Mckay 6 hours ago [-]
One of the reasons SQLite was mostly stable over the years was it sand-boxed its closed developer environment, and clearly defined the project scope. While controversial, they did not have to deal with common accountability issues associated with screening anonymous malicious and or incompetent clown PR. =3
A version controlled db? Have a look at dolts main page then, it’s been around for some time - this is just adding an embedded version.
thesz 2 hours ago [-]
There are filesystems (ZFS and btrfs) with snapshots and this feature can be used to version-control things. They both do copy-on-write and this is pretty close to what content-addressable storage would give you in terms of compression.
1718627440 2 hours ago [-]
If you want to take a version from a database, it's usually for backup. If you want different versions in your data, you put that IN the database. Manually merging different database versions does not sound too surprising.
A VCS is useful for code, because plaintext lacks a version feature. This problem does not exist for databases, because you design the structure yourself.
darkfloo 2 hours ago [-]
What problems does a version controlled database solves that is not solved by proper table auditing ?
zmmmmm 2 minutes ago [-]
not having to implement proper table auditing?
bawolff 4 hours ago [-]
I read it, and i think i understand even less than when i started.
grebc 3 hours ago [-]
They’re probably a VC backed product in search of a solution.
[0] - https://www.dolthub.com/blog/2019-10-14-dolt-a-simple-exampl...
But worse.
> Gas Town is for “write-only code”, … If you adopt Gas Town, you will lose the speed benefit of multiple agents if you read the code it produces. The first time you stare at an 8,500 line Git diff and try and parse what happened, you’ve lost. Go back to a single Claude Code session. Gas Town isn’t for you.
So none of the code has even been read by the author, it’s purposely overly verbose. “Touched by LLMs” seems to downplay just how vibe coded this is. I won’t use this database for anything.
From the article, at the end of the second paragraph:
> Could a team of agents pull it off? It only took about 2,000 pull requests but DoltLite going Beta proves a team of agents certainly could.
The first PR was merged March 17th.
"vibe coded" seems pretty fitting
Grouping it all under “vibe coded” loses precision. Sure, it uses AI, but differently from other projects and with different implications.
But the feedback loop was automated and accelerated. Instead of 1000 loops spread over 20 years, it had 1000 loops over a few months.
Calling it "vibe coded" just shows something about you, not the project. It is not production ready yet, but that is not for fast ai dev or for technical reasons. It needs independent reviews, independent verification, and reputation.
So when you say battle tested earlier, and then not production ready later - which one is it?
But anyway I assume that random name green account above is just a pro-vibe coding bot.
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.
Here's an in-memory one I made (pretty useful for unit tests): https://github.com/ncruces/go-sqlite3/tree/main/vfs/mvcc
The problem DoltLite solves is merging, not forking.
No? Where are you getting those figures? It feels like you may have pulled that from the 125 and 400 us numbers?
> 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 wouldn’t really solve what dolt does though.
> and it's level of testing and validation will be nothing like sqlite.
They’re using the other dolt tests as well as the SQLite tests. Nothing will hit the level of real world testing SQLite does.
https://www.dolthub.com/blog/2026-06-08-how-fast-is-doltlite...
This specific community has been a Schelling point for some of the worst engineering practices I've ever seen and a desire to abstract away all details of code to LLM personas like the "Refinery" and "Deacon"
https://www.youtube.com/watch?v=T4Upf_B9RLQ
A VCS is useful for code, because plaintext lacks a version feature. This problem does not exist for databases, because you design the structure yourself.