Glauber Costa

We're still welcoming, we still want people to come and build this with us. We just learned that the name doesn't matter.

We're still welcoming, we still want people to come and build this with us. We just learned that the name doesn't matter.

It does. And that's why what we decided to do is never port the server code to Limbo. Because then the server can be kept completely separate. And again, I think the reason we had the server and the client together was exactly because it was clear to us after a month or so that we would not, with LibSQL, with the fork,

It does. And that's why what we decided to do is never port the server code to Limbo. Because then the server can be kept completely separate. And again, I think the reason we had the server and the client together was exactly because it was clear to us after a month or so that we would not, with LibSQL, with the fork,

have achieved our goal of really just replacing SQLite, this goal that we had briefly. So the best strategy then became have the server code here as well, because now there are other things you can do with this open source project. But with the success of Limbo, again, it's back on the table and it's a very realistic goal that this will replace SQLite.

have achieved our goal of really just replacing SQLite, this goal that we had briefly. So the best strategy then became have the server code here as well, because now there are other things you can do with this open source project. But with the success of Limbo, again, it's back on the table and it's a very realistic goal that this will replace SQLite.

So we just revisited the strategy and said, this has to be just the client-side library exactly because of this, because we don't want to be in a position. And the name was a part of that. We just learned that it doesn't matter, right? But we don't want to ever be in a position. We want to design things in a way that we are never, ever, ever in a position to even think about

So we just revisited the strategy and said, this has to be just the client-side library exactly because of this, because we don't want to be in a position. And the name was a part of that. We just learned that it doesn't matter, right? But we don't want to ever be in a position. We want to design things in a way that we are never, ever, ever in a position to even think about

We would like to, you know, there's a contributor coming with this code and maybe we don't want to merge it because, you know, this might affect our business. You never want to be in this position. In fact, we want to make people in the community maintainers as well. We want to we want to have people hopefully like Preston, the person that I mentioned is in prison and others.

We would like to, you know, there's a contributor coming with this code and maybe we don't want to merge it because, you know, this might affect our business. You never want to be in this position. In fact, we want to make people in the community maintainers as well. We want to we want to have people hopefully like Preston, the person that I mentioned is in prison and others.

They're doing fantastic work. I mean, if they keep working for another six months. or a year, and you see that they're committed to the project, they should be maintainers as well. And they should have the ability to just merge code without talking to us. That's what we want to see. So the way we're going to structure things to make that happen is that our business now has to be just the cloud.

They're doing fantastic work. I mean, if they keep working for another six months. or a year, and you see that they're committed to the project, they should be maintainers as well. And they should have the ability to just merge code without talking to us. That's what we want to see. So the way we're going to structure things to make that happen is that our business now has to be just the cloud.

And then all the code for the cloud become, that is a separate project. That's going to be its own thing. And then the client, SQLite, for example, they don't have encryption at rest. They don't have a bunch of things because they do try to build a lifestyle business around it, as far as I understand, by selling those things. They're very specific. We want all of this in the open source for us.

And then all the code for the cloud become, that is a separate project. That's going to be its own thing. And then the client, SQLite, for example, they don't have encryption at rest. They don't have a bunch of things because they do try to build a lifestyle business around it, as far as I understand, by selling those things. They're very specific. We want all of this in the open source for us.

We want all of this. We want encryption at rest. We want all sorts of extensions. We want everything that runs on the client to be 100% open source.

We want all of this. We want encryption at rest. We want all sorts of extensions. We want everything that runs on the client to be 100% open source.

I think, yeah, I think if this was a consumer business is when your mom calls you to say that she's using it without knowing that this is the software they work with. I don't think my mom's going to use Limbo or Turso or SQLite or whatever. So I can't use that.

I think, yeah, I think if this was a consumer business is when your mom calls you to say that she's using it without knowing that this is the software they work with. I don't think my mom's going to use Limbo or Turso or SQLite or whatever. So I can't use that.

So the criteria for us is really when we can see somehow through some fuzzy metric that we've got, like we have a billion databases out there, right? So, you know, SQLite has a trillion databases. And I think that we don't think we're going to replace SQLite in a year, right? That's not the goal, right? But we think that in a year, we can get to this point where, hey, we got our first billion.

So the criteria for us is really when we can see somehow through some fuzzy metric that we've got, like we have a billion databases out there, right? So, you know, SQLite has a trillion databases. And I think that we don't think we're going to replace SQLite in a year, right? That's not the goal, right? But we think that in a year, we can get to this point where, hey, we got our first billion.