Deno, Ryan Dahl's JavaScript/TypeScript runtime, has raised seed investment and is converting itself into a company while keeping the project open source. The announcement goes out of its way to reject the usual monetization playbook:
For Deno to grow and be maximally useful, it must remain permissively free. We don't believe the "open core" business model is right for a programming platform like Deno. We do not want to find ourselves in the unfortunate position where we have to decide if certain features are for paid customers only.
The company says it has hinted at commercial applications of the infrastructure in past conference talks, and that its business will build on top of the open source project rather than monetize it directly.
What the runtime brings to the front end
Deno's "secure by default" execution model is the headline feature for developers with a security focus. Also notable is TypeScript support out of the box; TypeScript's share of the developer population has held near two-thirds, and the language's role in fully typed stacks — GraphQL included — keeps it relevant.
TypeScript and JSX are equally supported by the large next-generation build tools: Snowpack, Vite, and wmr. A dedicated Deno bundler, literally named Bundler, supports both as well.
Rust, Go, and the speed question
Deno is written in Rust, which matters partly for performance. Snowpack and Vite run on esbuild, written in Go and also fast. Whether Go or Rust wins for this kind of workload isn't settled, but either is a significant step up from most current bundlers and task runners. esbuild can be used directly or through thin wrappers such as Estrella — again, with TypeScript supported.
Where that leaves Babel
A fair question follows for Babel: if TypeScript isn't run through it, JSX doesn't need it, and basic ES6/7 compilation is no longer necessary given broad browser support, how long does it stay in pipelines? The realistic answer is a long time — a project of that size doesn't vanish. One exotic, desirable new JavaScript feature that compiles down to existing syntax would be enough to pull it back into everyone's build.



