glommer

Sorry to hear about that. That’s definitely not the norm, especially if this wasn’t on the free tier. We expect very low latency, but if it is a local isolated problem with a small group of servers our status page won't pick up. Though hard to say much more without the specifics.

Rob told me you were at Supabase now and I am STOKED to work together again, Paul!

No, I truly don't understand that. It is true that some acquisitions fail, but most of the ones you see failing are doomed from the start and are a way for the founder to exit, acquhire, etc.

I had a never-ending host of options at my hand. Turso grew revenue > 5x this year. I had no reason to accept an offer that wouldn't have a great chance of success.

I certainly am! A large part of the reason this happened is that I sat down with Paul, and he shared his vision with me for what he wanted to do with Turso and how that would fit the supabase story. Very exciting!

it's funny, because money is the number 1,000 or even lower thing on my priorities.

Turso has a booming OSS community with many contributors from outside the company and is fully MIT.

I hear you Josh, and I don't blame you because this does happen a lot. All I can say is that everyone is excited about this, on both sides of the aisle. From our perspective we'll have resources now to turbocharge the development of Turso, and things will only get better from here.

I shaved my head first, though.

Jarred is a copycat on that front.

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.

Write me a message to my email directly or hit me up on Discord.

We are very excited to be a part of Supabase

our cloud pays the bill just fine though.

Turso CEO here. We were doing fine.

This is a strategic acquisition and I fell in love with the vision Supabase had for how they would use Turso going forward.

More to come

lol

thank you!

Turso CEO here.

We were doing fine.

This is a strategic acquisition and I fell in love with the vision Supabase had for how they would use Turso going forward.

More to come

What you are pointing to did happen. What you are forgetting to mention is that this was one phrase in a post that was otherwise singing their praises.

The charitable interpretation is that when people pointed this out, I have read it, and come to agree that the wording was too strong and not representative of what we wanted to convey. Therefore, it was taken down.

But why be charitable when one can just throw accusations around from the armchair towards people one barely knows ?

The one thing you are right about, is that I am failing to live up to the Lord. As much as I try, I keep falling short. It happens not only here but in all aspects of my life. If it wasn't for his grace I would be in Hell for sure.

simon, you will be pleased to know that the python package for turso is in good shape! (and if you do find any issues please scream at us)

There is a lot of work that still needs to be done to make this production-ready, both from a performance and reliability point of view, as we did our best to convey on the blog. We truly appreciate you trying it out! Report any issues, please.

Yes, this is (one of) the point(s) you raised. You said there was a public an "unpleasant fight" (never happened) because of "criticism of SQLite" on my part. I calmly explained that such thing never took place. I have a preference towards Open models but never criticized SQLite (as in stated that they are wrong). Where does the unpleasant fight comes from?

Your claim that we are doing something ethically wrong seems to be informed by your pre-existing opinion of me, that itself derives from the "unpleasant fight" (that never happened).

As for the tagline we use, most people don't get the impression that there is any violation of ethics or respect. This is evidenced by other people's reaction here. You do, and you are within your right. I can't, unfortunately, please everybody.

Some people are more relevant than others, though: in this case, if the authors of SQLite expressed their opinion to me that this crosses a line in their view, I'd change it, without blinking an eye.

I have a tremendous respect for them, and we want our messaging to convey nothing but that!

The flag is --experimental-mvcc, it is in the help for the shell. You are right that the blog failed to mention. I will get this fixed soon!! Thanks for noticing it.

It's very easy to do given the async model. It is one of the new features that is working the best so far.

Linux was designed to run in home PCs, and we keep running it in supercomputers. It works just fine. Tools evolve.

Pekka is a Finn, and there are other Finns as well, but not all of us are Finns.

Our Finns are also not the standard Finns. I know Pekka closely for 15 years, and he smiled 3 times.

Thanks! Appreciate it, and you will see we came a long way with the implementation. It's now right around the corner! We'd love to see you try and report back your impressions.

I understood your criticism. I disagree with it, and I think we are not misrepresenting anything, as we make it very clear that we are not SQLite, we are just a reimplementation that goes beyond it (evolution).

The disagreement about their contribution model of course happened, but the meaning you ascribe to it, perhaps is something you imagined. It boils down to what you understand "criticism" to be.

If I see someone doing something wrong, I will criticize them. That certainly never happened. What happened is that we pointed out pros and cons of an open and closed development model. We believe a piece of technology that plays the role of SQLite would benefit from having an open model. And exactly because they are absolutely not doing nothing wrong with not being open, we created our own thing. Hard to see how that is a "criticism".

I said that a billion times, and here's a billion and one: there's absolutely nothing wrong with a closed model. SQLite is doing nothing wrong. They contributed tremendously to the databases we used every day.

I do think an Open model yields so many benefits that should someone rewrite SQLite with an open model, even starting 20 years later, they would end up ahead.

There is now a very easy way to prove or disprove this particular hypothesis.

Stay tuned!

You just have to pass the experimental flag. I thought this was explained in the blog ?

why not? Turso is a fully local database, you can just download the shell and use it as you would use sqlite.

Author of Turso here. Couple of points

* You are right not to rush. You should keep using SQLite until Turso matures. Some use cases are more tolerant to new tech than others. It will take time for us to reach the level of trust SQLite has for broad use cases, but we are hoping to add value for some use cases right away. Never rush, tech matters!

* I have never met Hipp, but only heard great things about him.

* We never had a fight with SQLite over their contribution model (or about anything for that matter, I never even met Hipp or anybody else from SQLite). We just disagree with it - in the sense that we believe in different things. We don't think what they do is fundamentally wrong. Different projects take different paths.

* We are not using the SQLite name. We compare ourselves to SQLite because we are file and API compatible, and we do aspire to raise the very high bar they have set. It is hard to do this without drawing the comparison, but we are a different project and state it very clearly. I am not a lawyer (and neither you seem to be), but we believe we are doing is okay. If we ever have any valid reason to believe we crossed a line here, we will of course change course.

* We are not "startup bros". We spent 20+ years of our lives building databases and operating systems.

yes, and obnoxious too. You should have seen me.

Preston has never asked for anyone's sympathy or understanding about his past crimes. If you read his stuff, he owns it fully, is incredibly sorry. He's the first to admit that what he did had very real consequences.