State of the Web: Deno
byteofdev.com
State of the Web: Deno
1–10 of 116 posts
Re: State of the Web: Deno
#2[deleted]
Re: State of the Web: Deno
#3Why is it that ES6 modules load only asyncly but Node.js CommonJS modules only syncly?
I find sync is often simpler to code for.
Re: State of the Web: Deno
#4I prefer CommonJS. It's so simple. You assign the dependency to a variable and that's it. I still need to look up the syntax every time I use ESM.
Re: State of the Web: Deno
#5> V8 is a sandboxed language
False, V8 is a JS runtime with sandboxing built into its core design. It’s not a language and it doesn’t guarantee sandboxing the JS runtime.
> that makes it impossible
False, breaking out of the sandbox is trivial in environments which allow native addons.
Re: State of the Web: Deno
#6Why is it that ES6 modules load only asyncly but Node.js CommonJS modules only syncly? I find sync is often simpler to code for.
Because the ESM standard specifies that modules are loaded by URL and themselves might initialize async. Once anything is async the whole call stack into it is. See also various discussions of “colored functions” which have made the rounds again recently.
Re: State of the Web: Deno
#7Mentions security and then completely glosses over security in the section on "yeah, we load random modules from URLs but it's okay because most Deno registries are immutable and we cache files"
Re: State of the Web: Deno
#8Offtopic but this webpage disables my bottom navigation bar on mobile safari, their own navigation on top re-enables this. Has anyone else experienced this?
Re: State of the Web: Deno
#9Deno is an interesting experiment, but I don't see it ever replacing nodejs, beyond the nodejs ecosystem eventually adopting it.
It is the usual case of worse is better, and nodejs for better or worse, does it job.
Re: State of the Web: Deno
#10Deno is an interesting experiment, but I don't see it ever replacing nodejs, beyond the nodejs ecosystem eventually adopting it. It is the usual case of worse is better, and nodejs for better or worse, does it job.
I beg to differ, Deno adds some fire to quality modules becoming the better norm for javascript on the server-side, smaller, faster, purpose-made modules and frameworks that don't rely on thousands of dependencies.
Of course, it's up to each and every developer that contribute, but looking at some of the most up-stared Deno modules, that's the direction it's heading.