I would add that Deno is a TypeScript engine, not a Javascript one. I think its adoption (and the adoption of Fresh) will come from enterprises which place big bets on TypeScript because of its static typing nature. The future will tell.
Deno will run JavaScript just fine and by default it simply strips the type annotations from TypeScript; it doesn't type check unless explicitly directed to do so. It's still based on V8 which is purely a JavaScript engine. I believe it's the WebAssembly portion where Deno leads the way. That's why there are opinions that WebAssembly will have a greater impact on the server/edge than on the client side.
So in a production deploy it still makes sense to output JavaScript.
TypeScript by default is seen as a plus but Deno can be successful even if TypeScript goes extinct.
I would add that Deno is a TypeScript engine, not a Javascript one. I think its adoption (and the adoption of Fresh) will come from enterprises which place big bets on TypeScript because of its static typing nature. The future will tell.
Deno will run JavaScript just fine and by default it simply strips the type annotations from TypeScript; it doesn't type check unless explicitly directed to do so. It's still based on V8 which is purely a JavaScript engine. I believe it's the WebAssembly portion where Deno leads the way. That's why there are opinions that WebAssembly will have a greater impact on the server/edge than on the client side.
So in a production deploy it still makes sense to output JavaScript.
TypeScript by default is seen as a plus but Deno can be successful even if TypeScript goes extinct.
Interesting, I didn't know that, thanks!