|
|
|
|
|
by Grimm1
1681 days ago
|
|
I see Deno getting a lot of play here, and I think rightfully so. The recent globally distributed chat example in like 20 lines of code is basically the level of accessibility I like seeing brought to otherwise very complicated distributed systems setups. That said how is Deno being seen in relation to Node, iirc Deno is being made to correct on a lot of the issues Node originally had but I’m curious about adoption and how this is going to fit in the JS world where Node has become so cemented, what’s the killer feature to move those people over? Or is that not the play, will this peacefully coexist? |
|
- no hassle with `node_modules`
- no hassle with `npm install` and `npm ci`
- no hassle with `package-lock.json`
- no hassle with `node-gyp`
- no hassle with setting up Typescript
On the nice to have side I would mention:
- opinionated take on linting, testing and formatting
- possibility to compile into self-contained executables