Deno is 4 years old now and is slowly maturing. Among other things, the Node alternative has become known for the really good security principles. Deno is running in a kind of sandbox, just like the browser sandbox. Many developers really like the idea. But how mature is Deno really? Is the effort of changing your runtime worth it if you are already familiar with Node? What’s still missing from the young competitor? Architecture expert Sebastian Springer answers these questions:
What is the most important security feature of Deno?
“The fact that you can manage access permissions to system resources. However, this should be taken with a grain of salt. I can a) leave it out and Deno asks me. Or b) make it explicit via options. Or c) turn off security with an option. If an application needs too many permissions and asks for them, one is quickly tempted to just choose option c).”
What do you have to get used to when you switch from Node to Deno?
Does it make sense to change from Node to Deno in existing projects?
“Personally, I continue to rely on Node in the large projects, the platform is stable, established and has a huge ecosystem to utilize. For small and medium projects, completed services or prototypes, Deno is definitely a very good solution. Even though Deno is already 4 years old, very important developments have taken place only in the last months and years. Like, for example, the collaboration with Node and the community.”
“I know that I need Deno when”
“…I implement small and modern applications, attach importance to additional security in the form of a sandbox. Concrete projects are also a great opportunity to learn the Deno way of doing things.”
What do you miss in Deno?
“What I miss with Deno is the stability of Node. There’s a lot happening under the hood right now, the community is growing and evolving. That’s excellent for me as a developer, I want to try new things. For my big project, sometimes I don’t want that flexibility and modernity.
About the author