[tarruda]

> Here I don't see how Deno is solving this , all the APIS seems again so barebone.. instead of having 1000+ dependency from NPM you'll have 1000+ dependency from remote URL

With Deno you can already do a lot with only what is provided by the main executable. Here's a subset of the available subcommands:

    bundle: Bundles JS. While it doesn't do everything that webpack does, it already provides enough to deploy SPAs. 
    coverage/test: Builtin test/coverage framework.
    fmt/lint: Builtin lint/formatter.

IMO these provide basic tools that are likely necessary for any JS project, yet with Node.js you need a few hundred NPM deps to achieve the same functionality.

Not to mention the builtin Typescript compiler. Starting a few of years ago, I don't even consider the possibility of creating a Javascript project without using Typescript as the main language. With Deno you have it builtin.

[jackosdev]

Oh yeah forgot about built in TS, didn't even know about the build tools. Interesting, might have to give it another run

[vagrantJin]

> Starting a few of years ago, I don't even consider the possibility of creating a Javascript project without using Typescript as the main ...

The truth value of this statement is suspect but..

In any case, why should typescript be the default when it compiles to JS? Why shouldn't js be the default in a js framework?

[tarruda]

I don't understand what you mean by "default". Deno simply provides a builtin compiler which allows it to run Typescript transparently. Clearly Deno also supports JS out of box.

[peterthehacker]

Isn’t typescript a superset of javascript so any ts compiler must also run js?