[juliend2]

After reading "A love letter to Deno"[1] I think I might actually start installing deno apps like this one on my home server.

Not only because they would be more secure by default, but also because Deno apps don't seem to need/want to be dockerized. Which means less overhead.

Not sure if it's a cultural thing or just some features of Deno that make Docker less necessary.

[1] https://matklad.github.io/2023/02/12/a-love-letter-to-deno.h...

[zja]

> Deno apps don't seem to need/want to be dockerized. Which means less overhead.

Why do you say that? I can’t think of any reason a Deno project wouldn’t benefit from Docker more or less any other application. There’s an official Deno Docker image, so I wouldn’t say that not using Docker is a part of Deno culture.

But I could see the single executable being easier to use than Docker if you’re just trying to run a script on a home server!

[JLCarveth]

The original commenter could be referring to Deno's permission system being similar to Docker's sandboxing, which could be true; I am not familiar enough with Docker to confirm that.

Personally, I tend to run my Deno/Node services using simple SystemD services rather than using docker or running the executable as-is.