Glauber Costa

And the story is always the same. The story is always the same. And it's exactly the thing I said. They were very excited about the prospect of a better SQLite. They knew about LibSQL, but LibSQL never enticed them because it just wasn't... In UC's word, it just wasn't crazy enough, which I translate to bold. But it just wasn't...

And the story is always the same. The story is always the same. And it's exactly the thing I said. They were very excited about the prospect of a better SQLite. They knew about LibSQL, but LibSQL never enticed them because it just wasn't... In UC's word, it just wasn't crazy enough, which I translate to bold. But it just wasn't...

it kind of caps where you can go because of all, you know, you still shackle by the fork. So when they saw this thing that, and I think you add this sprinkle to that as well too, man, there's so, this is a new project. So there's so many things to do, which engineers get attracted to, to some extent as well. But if you talk to them again, it's always the same story.

it kind of caps where you can go because of all, you know, you still shackle by the fork. So when they saw this thing that, and I think you add this sprinkle to that as well too, man, there's so, this is a new project. So there's so many things to do, which engineers get attracted to, to some extent as well. But if you talk to them again, it's always the same story.

I love the vision and I already loved the vision when I heard of Leap Sequel, but this thing here, is just the right amount of ambitious that I want to start devoting my time to that and I want to be a part of that as well.

I love the vision and I already loved the vision when I heard of Leap Sequel, but this thing here, is just the right amount of ambitious that I want to start devoting my time to that and I want to be a part of that as well.

So that's exactly, and we wanted to, one of the things that we said a lot in the early Leapsicle days is that we said that a lot because we heard from a couple of people, a couple of companies even, we love the idea of what you're doing because it gives us a seat at the table.

So that's exactly, and we wanted to, one of the things that we said a lot in the early Leapsicle days is that we said that a lot because we heard from a couple of people, a couple of companies even, we love the idea of what you're doing because it gives us a seat at the table.

And then my interpretation of that is that it turns out it's actually pretty hard to give people a seat at the table if you don't own the table. So Limbo gave us this. I mean, it's our table now. Now, it's a table that is modeled after another table. But we own the table and now we can really truly give those people a seat at the table.

And then my interpretation of that is that it turns out it's actually pretty hard to give people a seat at the table if you don't own the table. So Limbo gave us this. I mean, it's our table now. Now, it's a table that is modeled after another table. But we own the table and now we can really truly give those people a seat at the table.

I mean, they're coming, they're writing code, they're contributing, they're reviewing code, they're helping with the direction, they come out with ideas, things that we never consider, things that we never consider, things that will not be a priority. Like the thing, SQL already limbo runs on the browser. Somebody showed up today, today.

I mean, they're coming, they're writing code, they're contributing, they're reviewing code, they're helping with the direction, they come out with ideas, things that we never consider, things that we never consider, things that will not be a priority. Like the thing, SQL already limbo runs on the browser. Somebody showed up today, today.

Oh, I got LibSQL to compile, run the limbo CLI in WebAssembly and now I'm distributing the CLI. It's not even something we would have done, but the person took an interest because it doesn't have a ceiling. You essentially can take this anywhere.

Oh, I got LibSQL to compile, run the limbo CLI in WebAssembly and now I'm distributing the CLI. It's not even something we would have done, but the person took an interest because it doesn't have a ceiling. You essentially can take this anywhere.

Leap SQL came to be a little bit, and a part of that because, again, as I said, after we had this dream of replacing SQLite for 10 minutes, and then it became clear that it wouldn't happen. So we had this something that was very valuable. We knew it was valuable, but we had to struggle a little bit more with what do we do with that. So the Leap SQL project today is, again, it's two things.

Leap SQL came to be a little bit, and a part of that because, again, as I said, after we had this dream of replacing SQLite for 10 minutes, and then it became clear that it wouldn't happen. So we had this something that was very valuable. We knew it was valuable, but we had to struggle a little bit more with what do we do with that. So the Leap SQL project today is, again, it's two things.

It's a fork of SQLite. with some of those changes like vector search, but it is also, and it's all in the same repository. It's all part of the same project. It is also a server implementation to do serverless SQLite over the wire. So that is what, that is what lib SQL is. This will, it's, it's an open source project. So we're still going to be maintaining that, but the, the,

It's a fork of SQLite. with some of those changes like vector search, but it is also, and it's all in the same repository. It's all part of the same project. It is also a server implementation to do serverless SQLite over the wire. So that is what, that is what lib SQL is. This will, it's, it's an open source project. So we're still going to be maintaining that, but the, the,

The client side part is going to be full Limbo. We intend to eventually get all of those things we've done, like vector search, all of that. Leap SQL is still maintained for the time being because, again, we have a business around it. We have features that we depend on, but our goal is to eventually port all of those features to Limbo, which, again, we plan to rename to Turso.

The client side part is going to be full Limbo. We intend to eventually get all of those things we've done, like vector search, all of that. Leap SQL is still maintained for the time being because, again, we have a business around it. We have features that we depend on, but our goal is to eventually port all of those features to Limbo, which, again, we plan to rename to Turso.