Jerod Santo

All right, let's talk Deno 2. You said you guys kind of agonized over when you could call it a 2. This is always a hard problem, even for the folks who are trying to semver their projects, which is usually libraries, not so much runtimes. But hard problem. What's a major? What's a minor? Is this a patch? Of course, most majors in these cases are for...

All right, let's talk Deno 2. You said you guys kind of agonized over when you could call it a 2. This is always a hard problem, even for the folks who are trying to semver their projects, which is usually libraries, not so much runtimes. But hard problem. What's a major? What's a minor? Is this a patch? Of course, most majors in these cases are for...

uh, marketing purposes, which I think is totally fine. You got to get attention on what you've been up to and you can't just simply release things all the time and people just don't pay attention. So usually a 2.0 comes with it, a whole bunch of stuff. This one certainly does. You want to iterate over a few of the high points and we'll talk about them.

uh, marketing purposes, which I think is totally fine. You got to get attention on what you've been up to and you can't just simply release things all the time and people just don't pay attention. So usually a 2.0 comes with it, a whole bunch of stuff. This one certainly does. You want to iterate over a few of the high points and we'll talk about them.

Very cool. JSR is very interesting because the history of NPM is fraught with costs. It was a cost center. Effectively, it was infrastructure for all of us web developers and NPM Inc or whatever. I think that's what it is. NPM Inc became the entity that had to bear the burden of that cost of just hosting millions and millions and maybe trillions of downloads over the years.

Very cool. JSR is very interesting because the history of NPM is fraught with costs. It was a cost center. Effectively, it was infrastructure for all of us web developers and NPM Inc or whatever. I think that's what it is. NPM Inc became the entity that had to bear the burden of that cost of just hosting millions and millions and maybe trillions of downloads over the years.

And so JSR, I assume also must cost some money to run. How are you guys doing that? How's it working?

And so JSR, I assume also must cost some money to run. How are you guys doing that? How's it working?

is it the kind of thing where you would write a package and you would maybe put it on both registries for in the meantime, or does it matter? Like if I was going to author something, maybe I'd already know how to do all the crazy NPM things you have to do. Is it, I just post them both. Do I post a JSR? How does it, how do you suggest?

is it the kind of thing where you would write a package and you would maybe put it on both registries for in the meantime, or does it matter? Like if I was going to author something, maybe I'd already know how to do all the crazy NPM things you have to do. Is it, I just post them both. Do I post a JSR? How does it, how do you suggest?

Yeah, yeah, yeah. Yeah, totally. I agree with that. So as an author, I totally understand why JSR would be cool, especially if I'm an author of a package and I don't have all of the NPM know-how. As an end user who just has a package JSON in my Deno app or something, like why... does JSR help me or does it matter if I'm NPM installing JSR?

Yeah, yeah, yeah. Yeah, totally. I agree with that. So as an author, I totally understand why JSR would be cool, especially if I'm an author of a package and I don't have all of the NPM know-how. As an end user who just has a package JSON in my Deno app or something, like why... does JSR help me or does it matter if I'm NPM installing JSR?

That's awesome. And JSR modules don't lock you into Deno. Like you can use it in Node, you can use it in other things, right?

That's awesome. And JSR modules don't lock you into Deno. Like you can use it in Node, you can use it in other things, right?

So I'm here looking at a node server file I have on my machine that has import Fastify, import Puppeteer, and import AWS SDK. At this point with Deno 2, I could just Deno run this sucker, you think?

So I'm here looking at a node server file I have on my machine that has import Fastify, import Puppeteer, and import AWS SDK. At this point with Deno 2, I could just Deno run this sucker, you think?

That's really exciting.

That's really exciting.

I was thinking about trying it. Well, I don't have Deno 2 on this machine. I still have Deno 1. Can I just, I probably can't brew install.

I was thinking about trying it. Well, I don't have Deno 2 on this machine. I still have Deno 1. Can I just, I probably can't brew install.