DEV Community

Discussion on: Here's Actually Why Deno Flopped

Collapse
 
papito profile image
Andrei Taranchenko

First of all, in the Javascript world, the hype cycles are massive and unstoppable. By default, Deno should take off as a "better Node", especially since this is effectively Node 2 - from the same author.

Secondly, claiming that it does not have enough features to switch to does not check out. Businesses routinely choose to spend hundreds of hours and millions of dollars implementing and maintaining, say, Kubernetes, which the vast majority of companies has no business doing, as they simply don't have the type and scale of problems it was designed to solve.