Earlier quoted context omitted.
With merging updates between branches?
Physical or semantic merging?
DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs
61–65 of 65 posts
Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs
#62Earlier quoted context omitted.
Ah yes so the 4x slower isn’t really a real world case and you’d have to explicitly measure yours - it’s not a fixed slowdown but depends on table size - and it’s for doing many many single inserts in a row, which you’d be batching either way.
That's probably why they gave a range in their original comment.
Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs
#63Earlier quoted context omitted.
That's probably why they gave a range in their original comment.
Which isn’t correct, either for real world cases or worst case linear inserts.
Sure the benchmark does not measure a real world application, but I never claimed it was.
Do you have a better benchmark to share?
I thought I was being charitable by using a benchmark published by the database's own authors.
Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs
#64Earlier quoted context omitted.
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 [0] - https://www.dolthub.com/blog/2019-10-14-dolt-a-simple-exampl...
> 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
Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs
#65Earlier quoted context omitted.
Agentic development still requires human review and human ownership of PRs. This is vibe coded. Seems precise to me.
You can call it what you want I guess, but "vibe coded" around these parts is a simple pejorative, it means the authors don't know what the code does and the product is poor quality. Most successful agent-coded projects have a few essential features that it's worth calling out: 1) The human driving it has real domain expertise; 2) There's an oracle for correctness; 3) The agent has a real-world example to copy, adapt…