Rendered at 23:20:35 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
localhoster 4 hours ago [-]
It's so hard to trust a vibe coded software with something with a thing as valuable as data.
I see no reason why would anyone even bother checking this out, while there a trusted, battle scared, and non vibe-coded alternatives such as postgres, duckdb,boltdb,SQLite.
Sorry mate.
br1 3 hours ago [-]
Formal verification should catch vibe coding bugs.
They use TLA+ with TLC which model checks the write ahead log (a component of the system). But that only models the WAL protocol, not the actual Rust code and not the other 99% of the system.
Any formal verification is of course awesome to see though.
oinoom 2 hours ago [-]
The part that’s not clear to me is, does the spec actually align with what’s been implemented, or has the spec only been formally verified. I think the risk with vibe coding this sort of thing is that claude assures you the rust code implements the spec when it doesn’t
TZubiri 2 hours ago [-]
big words, either you are a genius, or it's AI slop and we'd be better off using write(). Don't think there's inbetween.
I see no reason why would anyone even bother checking this out, while there a trusted, battle scared, and non vibe-coded alternatives such as postgres, duckdb,boltdb,SQLite.
Sorry mate.
They use TLA+ with TLC which model checks the write ahead log (a component of the system). But that only models the WAL protocol, not the actual Rust code and not the other 99% of the system.
Any formal verification is of course awesome to see though.