Live data from Hacker News

Node.js built-ins on Deno Deploy

deno.com

1–10 of 112 posts

Re: Node.js built-ins on Deno Deploy

#7
post #5

I do wonder about the long-term effects of Deno being Node-compatible; will it result in only Node programming being done since "Deno will handle it fine" and thus Deno specific stuff will not be developed?

Deno being Node compatible is the "Embrace" in "Embrace, Extend, Extinguish".

Re: Node.js built-ins on Deno Deploy

#8

Hey folks - I worked on this. AMA

Hi, thanks for this. Question: Do all Node APIs work as-is? For instance, I opened an issue for Deno stdlib's Conn interface to expose more state (like the ones available in Node: ready, half-open, writable, pause, resume, closed etc) for sockets, but those are unimplemented: https://github.com/denoland/deno/issues/13636

Re: Node.js built-ins on Deno Deploy

#9

ironically, the more node js goes into Deno, the less likely I am to switch. imho they should stay the course and not include too much node stuff.

deno has some benefits (fast, included ts, linter, formatter, etc.), but without node compatibility, i will not switch to deno.

Re: Node.js built-ins on Deno Deploy

#10

Hey folks - I worked on this. AMA

Hi, thanks for this. Question: Do all Node APIs work as-is? For instance, I opened an issue for Deno stdlib's Conn interface to expose more state (like the ones available in Node: ready, half-open, writable, pause, resume, closed etc) for sockets, but those are unimplemented: https://github.com/denoland/deno/issues/13636

Most Node APIs work just like they do in Node, yes. Some are not yet implemented (like the ones you mentioned). We'll be addressing them in priority order based on user feedback and how many NPM packages are blocked by the given feature.
Post reply on HN