Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

dolthub.com

Post reply on HN
Print view View original

21–30 of 65 posts

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#21

Post by grebc »

throw234259 wrote: post #19
vrighter wrote: post #6

Why would I trust my data to a vibe coded database, over a battle tested, tested to hell and back one?

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…

Battle tested means deployed in production.

So when you say battle tested earlier, and then not production ready later - which one is it?

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#22

Post by grebc »

bawolff wrote: post #16
IanCal wrote: post #12

Earlier quoted context omitted.

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.

I read it, and i think i understand even less than when i started.

They’re probably a VC backed product in search of a solution.

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#24

Post by Sharlin »

solarkraft wrote: post #23
SipitenoMK wrote: post #8

Would be good, but why not to vibe code this database myself if I had a problem with my current database?

You’d have to do the relevant R&D and maintain the product.

"But Claude does that for me"

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#25

Post by [deleted] »

grebc wrote: post #21
throw234259 wrote: post #19

Earlier quoted context omitted.

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…

Battle tested means deployed in production . So when you say battle tested earlier, and then not production ready later - which one is it?

[deleted]

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#26

Post by solarkraft »

Skinney wrote: post #15
dekelpilli wrote: post #9

Earlier 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

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.

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#27

Post by postexitus »

throw234259 wrote: post #19
vrighter wrote: post #6

Why would I trust my data to a vibe coded database, over a battle tested, tested to hell and back one?

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…

This, from a 1 day old throwaway account, tells a lot.

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#28

Post by thesz »

IanCal wrote: post #12
bawolff wrote: post #7

I don't understand why you would want this.

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.

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.

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#29

Post by vrighter »

throw234259 wrote: post #19
vrighter wrote: post #6

Why would I trust my data to a vibe coded database, over a battle tested, tested to hell and back one?

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…

I don't trust AI testing. An automated loop == zero testing in my book.

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#30

Post by darkfloo »

IanCal wrote: post #12
bawolff wrote: post #7

I don't understand why you would want this.

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.

What problems does a version controlled database solves that is not solved by proper table auditing ?
Post reply on HN