Ryan Dahl

Well, it is MIT licensed. So you can go start a company and you can fork Deno and then you can release it under, you know, you can hire a bunch of engineers and work on it for two years and then license those changes under something else, right? And it's, you know, it could be that, you know, Deno goes in a different direction and the, you know, Deno 4 or whatever gets re-licensed

Well, it is MIT licensed. So you can go start a company and you can fork Deno and then you can release it under, you know, you can hire a bunch of engineers and work on it for two years and then license those changes under something else, right? And it's, you know, it could be that, you know, Deno goes in a different direction and the, you know, Deno 4 or whatever gets re-licensed

What we've built so far is MIT licensed and will be that way. And no, there's no legal system in which this is dictated other than my own integrity, right? And saying that this is what... that what we're doing as a company.

What we've built so far is MIT licensed and will be that way. And no, there's no legal system in which this is dictated other than my own integrity, right? And saying that this is what... that what we're doing as a company.

Well, I think it comes down to the business model. So you get into trouble with open core business models because you have to decide, are these features commercial features or are these free features? And that kind of aligns the incentives in a way.

Well, I think it comes down to the business model. So you get into trouble with open core business models because you have to decide, are these features commercial features or are these free features? And that kind of aligns the incentives in a way.

poor way where you're, you're basically, you know, stealing from the open source users to, to, uh, not stealing, of course, these people are developing it, but you know, the, the incentives are just kind of the, the commercial is pitted against the open source. And what I'm trying to do, I have long recognized this, you know, I want my business model to be orthogonal to the open source project.

poor way where you're, you're basically, you know, stealing from the open source users to, to, uh, not stealing, of course, these people are developing it, but you know, the, the incentives are just kind of the, the commercial is pitted against the open source. And what I'm trying to do, I have long recognized this, you know, I want my business model to be orthogonal to the open source project.

So it helps it, you know, we're developing a JavaScript infrastructure that can be used in many places. We don't sell a, you know, enterprise version of Deno with like special enterprise features. We sell hosting services, right? We sell things that are orthogonal to Deno itself.

So it helps it, you know, we're developing a JavaScript infrastructure that can be used in many places. We don't sell a, you know, enterprise version of Deno with like special enterprise features. We sell hosting services, right? We sell things that are orthogonal to Deno itself.

We're all we're all figuring it out. But, you know, I think it's it's really misplaced to, you know, look at somebody who is or anybody who is like putting out public free public domain stuff and say you are doing something wrong, like I mean, that's somebody else's time and energy that's being put into essentially free software, right? That's, you know, whatever happens with it in the future.

We're all we're all figuring it out. But, you know, I think it's it's really misplaced to, you know, look at somebody who is or anybody who is like putting out public free public domain stuff and say you are doing something wrong, like I mean, that's somebody else's time and energy that's being put into essentially free software, right? That's, you know, whatever happens with it in the future.

I mean, you know, at least that software is free and benefits humanity in some way. But, yeah, you know, I think a lot about this stuff and I really want to set up Dino as a company to not be in a position where it needs to be relicensed in the event that like I am somehow not part of the company. That's an inconceivable proposition right now. But, you know, who knows?

I mean, you know, at least that software is free and benefits humanity in some way. But, yeah, you know, I think a lot about this stuff and I really want to set up Dino as a company to not be in a position where it needs to be relicensed in the event that like I am somehow not part of the company. That's an inconceivable proposition right now. But, you know, who knows?

Yeah. So, uh, Deno does follow Sember, and there are breaking changes in this, but Deno 2 is really trying to, I guess I'm calling it marketing in some sense, just trying to give some weight to the changes that are coming in Deno. So a lot of it's backwards compatible. There are some minor breaking changes, but those are essentially just small API things that aren't super important.

Yeah. So, uh, Deno does follow Sember, and there are breaking changes in this, but Deno 2 is really trying to, I guess I'm calling it marketing in some sense, just trying to give some weight to the changes that are coming in Deno. So a lot of it's backwards compatible. There are some minor breaking changes, but those are essentially just small API things that aren't super important.

The big changes are the module system. The fact that the MPM, the ability to pull in MPM modules is like really good now. The fact that we support package JSON projects. So if you have like a package JSON with some scripts in it and some dependencies, like you can actually run those right out, right in Deno. And the introduction of JSR, which is kind of this newfangled competitor to MPM.

The big changes are the module system. The fact that the MPM, the ability to pull in MPM modules is like really good now. The fact that we support package JSON projects. So if you have like a package JSON with some scripts in it and some dependencies, like you can actually run those right out, right in Deno. And the introduction of JSR, which is kind of this newfangled competitor to MPM.

No, not a competitor in a way. It's a superset to MPM. It's a new package registry where you can share JavaScript and TypeScript code. And yeah, we are introducing some stability guarantees. Probably most people listening here don't care about that. But yeah, we're starting an LTS, a long-term support release, giving some better stability guarantees on not changing APIs in the future.

No, not a competitor in a way. It's a superset to MPM. It's a new package registry where you can share JavaScript and TypeScript code. And yeah, we are introducing some stability guarantees. Probably most people listening here don't care about that. But yeah, we're starting an LTS, a long-term support release, giving some better stability guarantees on not changing APIs in the future.