Deno 1.16 Release Notes
deno.com
Deno 1.16 Release Notes
1–10 of 14 posts
Re: Deno 1.16 Release Notes
#2That 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?
Re: Deno 1.16 Release Notes
#3Re: Deno 1.16 Release Notes
#4I 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 a…
Re: Deno 1.16 Release Notes
#5Where are we at with Deno in terms of gotchas? Can it be used comfortably end-to-end for an average project? Does it have enough features implemented that you don't end up needing to find workarounds in the middle of a project?
Re: Deno 1.16 Release Notes
#6The localStorage thing feels like a change in the security model. Unless I'm missing something, now without any permissions a program can save data between calls. I thought that without --allow anything it would be close to a pure function. I think it's easily worked around by specifying a temporary localstorage when running a program you want sandboxed more fully.
Re: Deno 1.16 Release Notes
#7I 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 a…
- 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
Re: Deno 1.16 Release Notes
#8I 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 a…
I can only speak from a node developer perspective but deno makes some promises that I would consider absolute killer features should they work as advertised: - 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…
Re: Deno 1.16 Release Notes
#9I know someone's going to ask about permissions making the invocation process a pain, so here's my advice for that: embed the permissions flags in the shebang line!
Re: Deno 1.16 Release Notes
#10I 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 a…
I can only speak from a node developer perspective but deno makes some promises that I would consider absolute killer features should they work as advertised: - 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…
That it can already do this is what brought me into doing some stuff with deno. It's just deno compile to make a self contained executable (don't forget permission flags). It's a bit large at over 40 MB, but honestly that's not something I'm going to care too much about given how straightforward and easy it is and since it's not that large.