Hacker News new | ask | show | jobs
by ecmascript 871 days ago
I have a deno app in production and it is working just fine. However, I still think node is superior when you self host when you are not using docker. Deno afaik still doesn't support any way of running one process for every CPU like the cluster module in Node.js.

I like to run my shit on the metal and without Docker and it feels like Deno was designed to run on Docker or some other kind of virtual containerized environment.

However, you can run it on node thanks to pm2, but I guess why even run on Deno in the first place?

2 comments

OTOH Deno can produce self-contained binaries. For me this is a plus, it makes distribution so much easier. I don't care if it's 100MB, I just want to have one file which I can throw on my server,
That feature has a bad history of refusing to run due to unsupported things you're using, just like deno bundle.
So does node.js nowadays. But yeah, I agree it is an awesome feature!
That’s overstating it a bit. As you can see, it’s an experimental, tedious, manual process with Node:

> Stability: 1 - Experimental: This feature is being designed and will change.

https://nodejs.org/api/single-executable-applications.html

Deno, on the other hand, has it as a supported, complete feature that’s very easy to use:

https://docs.deno.com/runtime/manual/tools/compiler

You can do it using Workers, just like you would in a web browser