Comment by vmg12
7 hours ago
This is great, I was a little worried that the turso project's future was tied to the success of turso the company and it has impacted a few of my technical choices and has resulted in me choosing sqlite over turso a few times.
I'll likely be choosing turso going forward for projects.
More to come, but Turso remains a product and SQLite remains their focus. Supabase/Postgres is the path as workloads grow and require it.
(disclosure: I work at supabase)
? are you seriously preferring a vibe coded project over the war tested sqlite?
1. I've looked at how Turso verifies the correctness of their db and I'm satisfied with it.
2. Turso supports features I want that don't exist and will not exist in sqlite.
I mean this is pretty obvious, I'm not using sqlite because it doesn't do what I want it to do. I also don't understand the repeated "sqlite is the best tested software" sentiment. I don't care if it's the best tested if it doesn't do what I want it to do.
> don't care if it's the best tested if it doesn't do what I want it to do.
That’s an interesting tradeoff, especially if this is a production grade application. Curious: what features is SQLite missing?
1 reply →
We started turso way before vibe coding became a thing, king. And these days we use AI, like most people, but still review all the code ourselves before it goes in.
Very disingenuous to call turso a vibe coded project.