Seems like some competition is a good thing!
Love to see the experimental npm support.
deno init is a bit silly imo.
Love to see the experimental npm support.
deno init is a bit silly imo.
It makes trying Deno for the first time frictionless, while placing learning pathways for both module layout and testing. It’s a small accelerant to learning – but one that probably reduces early churn on the learning pathway due to an unnecessary decision.
This command also means that the next 100 tutorials written about Deno will skip a step with `mkdir` and `touch` while standardizing the naming convention of _test.ts files clearly.
A little pebble can change the flow of a large river if it’s placed while the river is still a stream.
Just because Deno's blank project is literally just `/* main.ts */ console.log("hello world!");` doesn't mean that the `init` command is useless.
It's not useful if you are already aware how Deno works. The point of adding it is to help people who don't know. It's about discoverability.