4 ms·
Seems like some competition is a good thing! Love to see the experimental npm support. deno init is a bit silly imo.
by nchudleigh 4y ago
Seems like some competition is a good thing!
Love to see the experimental npm support.
deno init is a bit silly imo.
- colejohnson66 4y agoWhat's wrong with `deno init`? `npm init` has been a thing for years.
- peanut_worm 4y agoYeah but Deno doesn’t require package.json or anything like that. Seems sort of redundant.
- brundolf 4y agoFrom the sound of things, deno init basically just downloads a sample project- it's not creating actual boilerplate that you're going to keep using as you implement your real app
- IshKebab 4y agoYeah but that's what users want. `<project manager> init` is a de facto standard way to say "Ok, new tool that I don't understand, make me a blank project." 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.
- melony 4y agoIt's also missing git and gitignore.
- jitl 4y agoA tiny command like this seems trivial, but it actually plays an important role. 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.