text stringlengths 0 2.68k |
|---|
**Glauber Costa:** A lot of people are going to be early adopters. A lot of people, I think like -- our thesis is that it doesn't even support... Even without transactions, there's a lot of people that with a little bit more support on the read side, they can already use it, because a lot of workloads for SQLite... Lik... |
\[58:06\] So we want to be very aggressive with making releases, but the moment we're going to say "Hey this is stable..." And look, we can actually even give us more time, because it's a great commitment to say it's something is stable. I mean, people trust you that this is going to work. So we can take even more time... |
**Jerod Santo:** How does this all affect Turso the business, and how does it fit in? This is going to -- I assume it's going to be an MIT licensed thing, open source... |
**Glauber Costa:** Yeah, so our business is going to change. We announced recently a lot of -- what we need to do is that we need to simplify our product a lot. So we had very hard decisions to make. Again, it was a tough time for us to go through those decisions. But we kept the mission in front of us. We kept this id... |
A couple of features that we have, some of them that I love... A lot of users, unfortunately, got quite upset with that, obviously. I mean, features that they use, and came to trust, we will discontinue. So the way we're doing this is that if you're a paid user, after a cutout date, you're going to be allowed to keep u... |
We're still going to maintain our platform, but again, we think that having a single person just running the platform will be enough. And we're not going to be investing in having new features into the platform. So the platform will essentially go -- which is the Turso Cloud. It will essentially be a place where you ca... |
We're not going to be investing too much in new features, in frontend features, in quality of life features... The platform will essentially go into a freeze for a year. And the platform is pretty good. It's at a position that we can afford to do this. And then for one year, we're going to go all-in in getting Limbo to... |
**Adam Stacoviak:** When you get to that place, whenever Limbo becomes Turso and Turso Cloud goes away, how will you differentiate this new launch? |
**Glauber Costa:** No, Turso Cloud doesn't go away. What is Turso today becomes called Turso Cloud. And then Turso, the embedded database just becomes Turso. And again, this is a lesson that we learned, and not that we haven't heard this before, but I think we're just stubborn... People kept telling us, it's very hard ... |
\[01:02:29.09\] And then when we announced our changes to the Turso platform, we had many questions from many people about "Hey, this feature they're going to discontinue, this other thing they're not going to support", and what happens is nobody asked about the name. Nobody said, "Well, with the name Turso--" Nobody c... |
And Turso today, again, is the cloud offering that is going to be renamed to Turso Cloud. And then what is Limbo, which is the client offering, will just be renamed to Turso, and that's it. And we're still welcoming. We still want people to come in and build this with us. We just learned that the name doesn't matter. |
**Jerod Santo:** How do you manage that relationship between the open source Turso, the interests of Turso Cloud, third party contributors who may want Turso to go a different direction, that maybe you don't want it to? Success brings all kinds of challenges. |
**Glauber Costa:** 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 will not, with LibS... |
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 j... |
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 - that is a separate project; that's going to be its own thing. And then the client... SQLite, for example, they don't have they don't have encryption at REST, they don't... |
**Jerod Santo:** \[01:06:05.06\] Very cool. So how will you know when Limbo/Turso has made it, has arrived, has replaced SQLite? Will it be on Mars? Will it be on trillions of devices? When will you think it's here, it's arrived? |
**Glauber Costa:** 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. 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 it's really when we can see s... |
So the first milestone that we have in mind is when we can, through some proxy, because a lot of that you cannot measure... But we have a good level of confidence that we have a billion databases in the open. Then I think "Okay, that's success." |
**Jerod Santo:** If people wanted to play with it today, how much is there? What could you play with, if anything? |
**Glauber Costa:** A lot of the read stuff works. A lot of the read stuff works. And one of the things that Pekka -- this was entirely Pekka's idea, that he did very well, and he was very praised by a lot of people, including those contributors... Some of them said "This is one of the reasons I contributed." It's that ... |
**Jerod Santo:** Adam, any other questions for Glauber before we let him go? |
**Adam Stacoviak:** I'm just trying to understand this future, I suppose... And I'm trying to piece it together, and I don't know how to ask this question necessarily, but I'm reading your most recent roadmap where you mentioned "Changes to our server implementation." And sorry for my stuttering, because I'm still dras... |
**Glauber Costa:** More or less, because -- yeah, just to add to that; it wasn't something very relevant, so I didn't bring it up... But we already had -- for other reasons, we already had a proof of concept of a new server implementation, that is not based on LibSQL. And the reason we did this is that we also want our... |
**Adam Stacoviak:** Okay. |
**Glauber Costa:** So that new server will be closed source. So that's one of the changes in strategy that we're making. And again, we understand that in a perfect world, everything will be open source. I would love that. But the reason we're doing this is that we want to have this very clear separation, without concer... |
\[01:10:01.14\] So that's going to be the dividing line. And then LibSQL still exists as a reference implementation. If you truly want to run an open source version -- I think it's more accurate to say if you want to run an open source implementation of our cloud platform, LibSQL will do this for you, with limitations.... |
**Adam Stacoviak:** 200%, gotcha. So in the future, when somebody runs Limbo, which will be renamed Turso, they can run that on their own. But if they want this massive scale multi-tenant world, they've got to host with you. |
**Glauber Costa:** Yes, or write their own implementation. Or use LibSQL, again, which is still going to be there, but we believe our implementation is going to be better. That's why we did it. |
**Adam Stacoviak:** So you're long betting on hosting a lot of databases in the future. |
**Glauber Costa:** Yes, yes. |
**Adam Stacoviak:** Okay. You said you don't need money, right? So you have the runway for the next 15 months. You get in danger if -- |
**Glauber Costa:** No, we have runway for more than that. Everybody needs money. |
**Adam Stacoviak:** No need to raise more now though, to get to this goal. |
**Glauber Costa:** We don't need to raise more money now, yeah. That's right. For more than two years. I've been talking about 15 months, not as a cutoff point for that. It was more about when do we believe that this can become... But we have capital for a lot longer than that. |
**Adam Stacoviak:** Okay, good. Let's talk in a year, I guess. I mean, that's all the questions I have for now, for the most part... Everything else is speculation, but there you go. |
**Glauber Costa:** Send me an invitation today, for a year in the future. |
**Adam Stacoviak:** January 22nd, 2026... |
**Glauber Costa:** Same time, same date... How about that? |
**Adam Stacoviak:** Exactly. |
**Jerod Santo:** Let's do it. |
**Glauber Costa:** Let's do it. |
**Jerod Santo:** Alright. Thanks, Glauber. Hey, we're rooting for you. This is really exciting stuff. |
**Glauber Costa:** Thank you. |
• Vite's origins as a solution to a Vue bug reporting issue |
• Evan You's initial prototype, vue-dev-server, which allowed loading Vue single file components without a build step |
• The addition of support for TypeScript and native ESM imports |
• The development of Vite's hot module replacement feature |
• Comparison with other tools, including Snowpack and Wmr |
• Vite's transition from a Vue-specific tool to a more general-purpose dev environment tool |
• The rewrite of Vite's internals to support multiple file formats and plugins |
• Discussion of Vite's development and release timeline, including the decision to skip version 1.0 and go directly to version 2.0 |
• Impact of Vite 2.0 on adoption and support, particularly in the context of other frameworks embracing Vite |
• Trajectory of Vite's development and its relationship to Vue.js, including the switch from Webpack to Vite as the default build tool |
• Evan You's approach to fostering communities and encouraging contributions to his projects, including acknowledging and empowering passionate contributors |
• Discussion of Vue's sponsorship and team organization |
• Comparison between Vue and Vite, including the circumstances surrounding Vite's development |
• The story of Matias joining the Vite team and his role in its growth |
• The formalization of the Vite team and the recognition of its members |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.