Short answer: overall, JavaScript containers will not overtake regular (Linux) containers. However, they will probably overtake them in specific use cases like running a server etc.

But there are several things to have in mind:

JavaScript Containers Are Deno Containers

Before JS container become a thing, Deno needs to become a thing. Like with any new technology, people always like someone else to test it first.

Yes, everything is fine for your cool little side project, but no one wants to spend thousands of dollars on development just to find out they need to port it back to Node.js before whatever issues are fixed.

And we are nowhere near widespread adoption of Deno.

Also, even though these two situations are not the same, but it reminds me somewhat on Python2 and Python3 problems. And I really hope this doesn’t happen with Deno and Node.

Porting Existing Projects

The reason Cobol (ancient programming language) is still “not dead” is because some critical software is using it.

And it would be:

  • too expensive
  • too risky
  • and too pointless

to port it to some more “modern” programming language. And the same will be with Node and Deno.

New projects will be probably started in Deno but majority of available jobs will be in Node. Which will take part in splitting the community somewhat.

Not saying this will be a huge issue, but an issue nonetheless.

Container “Inception”

“I had a Linux container withing a Linux container within…”

Good things about having a JavaScript containers is you don’t have to spin up so many Linux instances for no reason. You can have your base Linux instance and then just run JavaScript on top of it.

This will remove one layer of abstraction, meaning you don’t have to run an entire new OS just to start a simple process (like listening on a port for your server).


Overall I think this is a great idea and I can’t wait to see how this will look in real world applications

P.S. -> read this article if you want to double your salary