The reasons why node.js can't be a new dominance in backend development

NotFound404 - Sep 10 - - Dev Community
  1. Npm conducted a very wrong version illusion: Semver, assuming that libraries can always deliver a correct version obey Semver's rules.
  2. Npm then add the ability to auto update so called version range without any test and check up, which totally ruined the stability for a node project and consistency. Now, the node ecosystem is still a mess and only played by the frontend ecosystem which needs almost no stability and consistency.
  3. Advocate green keeper to force all packages to updated which eventually exhausts developers.
  4. Node.js has no good backend frameworks. express is very simple, sails is very slow, koa is very wrong and aex comes up very late.

Also npm added package lock trying to keep the packages stable, but the timing can never be back again and some developers have leave the node.js community for not able to see the future improvement.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terabox Video Player