Deno 1.0

Congratulations on the 1.0 release! I've been using Deno as my primary "hacking" runtime for several months now, I appreciate how quickly I can throw together a simple script and get something working. (It's even easier than ts-node, which I primarily used previously.)

I would love to see more focus in the future on the REPL in Deno. I still find myself trying things in the Node.js REPL for the autocomplete support. I'm excited to see how Deno can take advantage of native TypeScript support to make a REPL more productive: subtle type hinting, integrated tsdocs, and type-aware autocomplete (especially for a future pipeline operator).

Re: Deno 1.0

#6

Post by kalium-xyz » Wed, May 13, 2020, 10:43 PM UTC

Finally we can use it on production, great work everyone involved in making this happen!

Re: Deno 1.0

#7

Post by ravenstine » Wed, May 13, 2020, 10:44 PM UTC

Are imports async by default in Deno? That seems to be how it works given that you can import from a URL. This is interesting since async imports are currently a part of JavaScript(or at least a proposal?) by using the `import()` function.

Re: Deno 1.0

#8

Post by indemnity » Wed, May 13, 2020, 10:44 PM UTC

seleniumBubbles wrote: post #5

Congratulations on the 1.0 release! I've been using Deno as my primary "hacking" runtime for several months now, I appreciate how quickly I can throw together a simple script and get something working. (It's even easier than ts-node, which I primarily used previously.) I would love to see more focus in the future on the REPL in Deno. I still find myself trying things in the Node.js REPL for the autocomplete support.…

Seconded, a Deno TS REPL would be amazing, but they probably have a few bigger fish to fry yet :)

Re: Deno 1.0

#9

Post by threatofrain » Wed, May 13, 2020, 10:45 PM UTC

> Internally Deno uses Microsoft's TypeScript compiler to check types and produce JavaScript. Compared to the time it takes V8 to parse JavaScript, it is very slow.

> Early on in the project we had hoped that "V8 Snapshots" would provide significant improvements here. Snapshots have certainly helped but it's still unsatisfyingly slow. We certainly think there are improvements that can be done here on top of the existing TypeScript compiler, but it's clear to us that ultimately the type checking needs to be implemented in Rust.

> This will be a massive undertaking and will not happen any time soon; but it would provide order of magnitude performance improvements in a critical path experienced by developers. TSC must be ported to Rust. If you're interested in collaborating on this problem, please get in touch.

Re: Deno 1.0

#10

Post by firloop » Wed, May 13, 2020, 10:47 PM UTC

For the uninitiated, worth noting that one of the names on this post, Ryan Dahl, was the original node.js developer.