Ryan Dahl

And we're not quite sure if we want to go further down this route. I actually want to decouple the KV APIs from the Deno runtime itself and have them be a module that you pull in. You should be able to pull in JSR at Deno slash KV. There's no real reason that it needs to be built directly into the runtime. That's just for ease of implementation, essentially.

And we're not quite sure if we want to go further down this route. I actually want to decouple the KV APIs from the Deno runtime itself and have them be a module that you pull in. You should be able to pull in JSR at Deno slash KV. There's no real reason that it needs to be built directly into the runtime. That's just for ease of implementation, essentially.

Yeah. And, and it is, it is not safe. Yeah. Just to clarify, it is not stabilized in Dino too. So it's not something that we are necessarily supporting indefinitely. I guess it likely will be moved. But, you know, nevertheless, the DenoKV stuff is pretty awesome to you.

Yeah. And, and it is, it is not safe. Yeah. Just to clarify, it is not stabilized in Dino too. So it's not something that we are necessarily supporting indefinitely. I guess it likely will be moved. But, you know, nevertheless, the DenoKV stuff is pretty awesome to you.

I don't know if you played around with it at all, but like our other stuff, it's just freaking delightful to have like a easy state store. But yeah, there's a lot of questions to think through with that because, yeah, obviously a lot of people need a bit more of a complex database than a KV store. And like real application code actually needs a relational database to

I don't know if you played around with it at all, but like our other stuff, it's just freaking delightful to have like a easy state store. But yeah, there's a lot of questions to think through with that because, yeah, obviously a lot of people need a bit more of a complex database than a KV store. And like real application code actually needs a relational database to

Yeah, I think there's a lot of ideas around here, probably more inspired by Bun that did that.

Yeah, I think there's a lot of ideas around here, probably more inspired by Bun that did that.

I think it's a little, yeah, there is a little bit questionable because, I mean, you can always pull this stuff into packages. And there's always the question of, like, where's the runtime concern and what belongs outside of it? And it's always a difficult discussion. It's hard to have kind of an algorithm for deciding that. Yeah.

I think it's a little, yeah, there is a little bit questionable because, I mean, you can always pull this stuff into packages. And there's always the question of, like, where's the runtime concern and what belongs outside of it? And it's always a difficult discussion. It's hard to have kind of an algorithm for deciding that. Yeah.

You know, if Node does stabilize that API, because Deno does implement the Node built-in APIs, we will implement that. And of course, we have SQLite. We already use SQLite in there. So it'd be a pretty trivial matter to add that.

You know, if Node does stabilize that API, because Deno does implement the Node built-in APIs, we will implement that. And of course, we have SQLite. We already use SQLite in there. So it'd be a pretty trivial matter to add that.

That's what's exciting about JavaScript, right? It's, it's just like, it's it's, it's madness. It's chaos. But, but it's, it's just kind of yeah, there's, there's so many people with different ideas and everybody's inventing new things all the time. I think it's, it's really fun.

That's what's exciting about JavaScript, right? It's, it's just like, it's it's, it's madness. It's chaos. But, but it's, it's just kind of yeah, there's, there's so many people with different ideas and everybody's inventing new things all the time. I think it's, it's really fun.

We do. I feel like I shouldn't talk about it at this state. We have like new commercial efforts underway that are under heavy development right now, but it's a little too soon to talk about it publicly.

We do. I feel like I shouldn't talk about it at this state. We have like new commercial efforts underway that are under heavy development right now, but it's a little too soon to talk about it publicly.

Once 2.0 is stabilized, I think there are a lot of cleanups to do. I think there is still kind of a long list of node compatibility to work on. I think making the LSP faster is something that we'll be looking at. I think we removed Deno Bundle for 2.0. because we didn't have a great bundling story, but that bundling is obviously part of the JavaScript tool chain.

Once 2.0 is stabilized, I think there are a lot of cleanups to do. I think there is still kind of a long list of node compatibility to work on. I think making the LSP faster is something that we'll be looking at. I think we removed Deno Bundle for 2.0. because we didn't have a great bundling story, but that bundling is obviously part of the JavaScript tool chain.

And we think that that's something that Deno ought to provide. It's just, in general, bundling is a pretty hard problem to solve. It's not just simply bundle the script. There's all sorts of things you need to consider, and there's just tooling that is purpose-built for that that is much better, like ESBuild, for example.

And we think that that's something that Deno ought to provide. It's just, in general, bundling is a pretty hard problem to solve. It's not just simply bundle the script. There's all sorts of things you need to consider, and there's just tooling that is purpose-built for that that is much better, like ESBuild, for example.