4 ms·
> This article made me confirm my suspicion about Node.js > Becoming the new PHP > Kids ... > Many of them, also, rely on MongoDB, the Snapchat of Databases
by allover 9y ago
> This article made me confirm my suspicion about Node.js
> Becoming the new PHP
> Kids ...
> Many of them, also, rely on MongoDB, the Snapchat of Databases
These generalizations aren't helpful. Please don't pretend this wasn't an opinion you'd already formed.
- flavio81 9y agoI'm speaking about a real problem with the node.js community, and I say this as a user of the platform. The entry barrier is small and this creates some problems, not only the lack of security considerations on lots of web apps out there, but also on the quality of some NPM packages out there. Don't get me wrong, node.js is a good idea, but as ponted out by mikacsika's comment below: "Also, a lot of Node.js teams popping up from development shops et al consist of front-end engineers that have never needed to understand the systems-level impact of their code" One of my responsibilities is assisting a small start-up implemented in node.js. Guess what? A site developed exclusively by frontend developers. I pointed out many problems with the code, including security concerns. They were reluctant to implement the many changes i recommended, acting as if the targeted-to-frontend-turned-fullstack tutorials were always right... until their server and db got hacked 15 days ago. True story.
- allover 9y agoAnd I believe you. I still don't think that's a problem exclusive to Node. I've seen godawful, naive, insecure codebases written in C, C++ and PHP. I've talked to co-workers about similar experiences in Python, ColdFusion ... This 'Node people are the worst because they came from the front-end' attitude is poison.