2 ms·
To quote Aaron Sorkin somewhat out-of-context: "If liberals are so fucking smart, how come they lose so goddamn always?" I don't want to say that javascript is
by civilian 11y ago
To quote Aaron Sorkin somewhat out-of-context: "If liberals are so fucking smart, how come they lose so goddamn always?"
I don't want to say that javascript is a good language, but it can get the job done. And nodejs' value comes from allowing devs who have only had client-side experience to quickly jam on the server-side.
- mschuster91 11y ago> And nodejs' value comes from allowing devs who have only had client-side experience to quickly jam on the server-side. And this leads to clusterfucks like the Trend Micro Remote Command Execution clusterfuck a couple of days ago (https://code.google.com/p/google-security-research/issues/detail?id=693 https://code.google.com/p/google-security-research/issues/de...). It took a decade until enough braindead morons got away from PHP to fix its underlying deficiencies (like mysql_x, register_globals, ...); I'm afraid the same (or worse!) will happen to NodeJS. Reason: On client you can get away with a LOT more crap than on server because the browser will protect you from the worst (SOP, memory, infinite loops, ...), and so people aren't used to think about security or best practices or code size or code quality. Or about memory leaks. On the server you're left on your own - and to make crap worse, a PHP app always starts in a clean state, so unless you use external services, given the same inputs you will get deterministic behavior from your script. NodeJS not, yummy memory leaking bugs <3. Happy debugging!