Deno 1.20

#1

Post by Mikkel-T » Thu, Mar 17, 2022, 2:00 PM UTC

Re: Deno 1.20

#2

Post by msoad » Thu, Mar 17, 2022, 2:17 PM UTC

Has anyone tried switching from Node to Deno in an existing project? I'm personally very interested in Deno but it's hard to find a greenfield project to try it out and writing toy programs is not giving me enough insights of how much better/faster Deno is.

Re: Deno 1.20

#3

Post by yulaow » Thu, Mar 17, 2022, 2:29 PM UTC

msoad wrote: post #2

Has anyone tried switching from Node to Deno in an existing project? I'm personally very interested in Deno but it's hard to find a greenfield project to try it out and writing toy programs is not giving me enough insights of how much better/faster Deno is.

Honestly not and for a simple reason: there is nothing in deno that I need and can't find in node, but there are a lot of libraries in node that I need and I can't use them in deno. Simple as that

Re: Deno 1.20

#4

Post by jitl » Thu, Mar 17, 2022, 2:33 PM UTC

msoad wrote: post #2

Has anyone tried switching from Node to Deno in an existing project? I'm personally very interested in Deno but it's hard to find a greenfield project to try it out and writing toy programs is not giving me enough insights of how much better/faster Deno is.

I have enough trouble upgrading Node versions in serious projects. I don’t think it makes sense to convert a big existing project.

Re: Deno 1.20

#5

Post by encryptluks2 » Thu, Mar 17, 2022, 2:33 PM UTC

yulaow wrote: post #3

msoad wrote: post #2

Has anyone tried switching from Node to Deno in an existing project? I'm personally very interested in Deno but it's hard to find a greenfield project to try it out and writing toy programs is not giving me enough insights of how much better/faster Deno is.

Honestly not and for a simple reason: there is nothing in deno that I need and can't find in node, but there are a lot of libraries in node that I need and I can't use them in deno. Simple as that

Such as? Do you mean things in the standard library or like JS packages?

Re: Deno 1.20

#6

Post by tentacleuno » Thu, Mar 17, 2022, 2:35 PM UTC

encryptluks2 wrote: post #5

yulaow wrote: post #3

Earlier quoted context omitted.

Honestly not and for a simple reason: there is nothing in deno that I need and can't find in node, but there are a lot of libraries in node that I need and I can't use them in deno. Simple as that

Such as? Do you mean things in the standard library or like JS packages?

Probably both. You can't use NPM (though you can use one of those online CDN's like unpkg) and the packages you can use probably don't work, as Deno doesn't support Node's API at all. It doesn't support any Node-specific packages like 'fs' or 'crypto' either.

Unless you're writing a totally new application and don't need anything (even retrospectively) from NPM, Deno probably won't work for you.

As much as I like Deno as a concept, I can't really use it. Making a totally new JavaScript runtime with new API's and no compatibility with the current largest runtime is a very ambitious goal, and I hope they succeed with it nevertheless.

Re: Deno 1.20

#7

Post by mcraiha » Thu, Mar 17, 2022, 2:41 PM UTC

msoad wrote: post #2

Has anyone tried switching from Node to Deno in an existing project? I'm personally very interested in Deno but it's hard to find a greenfield project to try it out and writing toy programs is not giving me enough insights of how much better/faster Deno is.

Maybe someone working with a library project can answer that. Trying to replace node with deno in e.g. React + NPM project might be way too complicated.

Personally I won't taking part in any node projects anymore.

Re: Deno 1.20

#8

Post by erikpukinskis » Thu, Mar 17, 2022, 2:42 PM UTC

encryptluks2 wrote: post #5

yulaow wrote: post #3

Earlier quoted context omitted.

Honestly not and for a simple reason: there is nothing in deno that I need and can't find in node, but there are a lot of libraries in node that I need and I can't use them in deno. Simple as that

Such as? Do you mean things in the standard library or like JS packages?

I was playing with Deno for a side project about 6 months ago but stopped because none of the WebRTC handshake modules were supported.

I tried to push through and port one of them, but the base Node Socket library was missing most of the methods.

Deno looks awesome though, I can’t wait to take another look when it’s a little more mature!

Re: Deno 1.20

#9

Post by ignoramous » Thu, Mar 17, 2022, 2:45 PM UTC

msoad wrote: post #2

Has anyone tried switching from Node to Deno in an existing project? I'm personally very interested in Deno but it's hard to find a greenfield project to try it out and writing toy programs is not giving me enough insights of how much better/faster Deno is.

> ...enough insights of how much better/faster Deno is

We moved our Deno project to Node because of lack of lower-level APIs on Deno's Conn interfaces [0][1], but otherwise for our use-case (lots of tiny HTTPS connections) Deno absolutely blew Node out-of-the-water. Even at p50 (100tps) Deno (v1.18) was 10x faster than Node (v17.x) [2]

RAM wise, I found Deno (v1.18+) use 10M or so higher for the same code-base.

DevEx wise, Node is miles away from Deno, but it might get there in-time, or it might not [3]. I'd imagine, what may also work in Deno's favour in terms of IO-bound workloads, is the underlying tokio layer (vs libuv in Node).

API wise, Deno (comparatively) feels quite raw.

[0] https://github.com/denoland/deno/issues/13636

[1] https://github.com/denoland/deno/issues/9109

[2] https://github.com/nodejs/undici/issues/1203#issuecomment-10... | Explanation: https://github.com/RafaelGSS/nodejs-bench-operations/pull/3#...

[3] https://www.youtube-nocookie.com/embed/M3BM9TB-8yA