Typescript: Your thoughts on deno?

Created on 8 Jun 2018  路  4Comments  路  Source: microsoft/TypeScript

Ok, it's Friday, hopefully a bit of OT is acceptable :)

I just watched this fascinating talk by Ryan Dahl, the original creator of Node.js, on 10 things he regrets about Node.js. He also discusses deno, "a secure TypeScript runtime on V8" prototype.

Some quotes I found interesting:

  • "Inside the V8 itself, you have the TypeScript compiler, built into this whole executable." 19m45s
  • "I love TypeScript. It is the best thing." 19m53s
  • "I want this thing [deno] to do TypeScript, because I like it." 20m53s
  • "At the moment, its startup time is quite slow, it's like at one second which is completely unacceptable. However, I'm working on using V8 snapshots to snapshot the entire compiler, and plus other optimizations, and I'm fairly confident that it can be improved greatly." 22m47s

I'm not at all technical enough to understand everything he's doing inside V8 but it sure sounds exciting. What do you guys think?

Discussion

Most helpful comment

We were pretty happy to hear that Ryan likes TypeScript, especially since he's been such a huge part of the JavaScript community. We've recently been in touch with him to hear some more about the direction, but we think it's exciting to see where deno goes since there's a lot of space for innovation. Wherever it does end up, we'd be happy to see how we can help. 馃槂

All 4 comments

We were pretty happy to hear that Ryan likes TypeScript, especially since he's been such a huge part of the JavaScript community. We've recently been in touch with him to hear some more about the direction, but we think it's exciting to see where deno goes since there's a lot of space for innovation. Wherever it does end up, we'd be happy to see how we can help. 馃槂

Chiming in (knowing I'm not the target of this question!) -- I am SO psyched about deno, and hearing Dahl say he loves TypeScript was super validating to me as a TS lover. I'm super curious to see how deno might influence the future of TypeScript (e.g. will there ever be a future in which TS compiles directly to bytecode?).

FWIW, Deno has decided to remove all TypeScript for internal code: https://github.com/denoland/deno/pull/4750

@aphix From the document you linked:

Update June 10 2020: I saw that this design doc was being discussed more widely. Most people don't have the context to understand this narrow technical document - it is only applicable to a very particular, very technical situation in the internals of Deno. This is not at all a reflection on the usefulness of TypeScript in general. It's not a discussion about any publicly visible interface in Deno. Deno, of course, will support TypeScript forever. A website or server written in TypeScript is a very very different type of program than Deno - maybe much more so than novice programmers can appreciate - little of Deno is written in TypeScript. The target audience is the 5 to 10 people who work on this particular internal system. Please don't draw any broader conclusions.

Was this page helpful?
0 / 5 - 0 ratings