News for hackers. Stuff that matters.
Re:Pushing the performance limits of Node.js by betenoire on Thursday August 27, 2015 @04:46PM (#10131978)
considering how many "packages" are implicitly provided by a traditional LAMP stack, it's not _that_ surprising.

You want cookies? package. Sessions? package. promises? package*. make http requests? package. templating? package. hashing algorithm? package. You get the picture. If I had to replace every PHP function I use with a package, I'd end up with just as many packages.

Re:Pushing the performance limits of Node.js by KAdot on Thursday August 27, 2015 @05:21PM (#10132190)
That's the problem. In Python, Ruby or even PHP you usually just pick a function / module from the standard library, in Node.js you need to choose one from ~10 quite similar and quite popular third-party packages.
Re:Pushing the performance limits of Node.js by kaoD on Thursday August 27, 2015 @10:27PM (#10133436)
> In Python, Ruby or even PHP you usually just pick a function / module from the standard library

Which is usually rotten for the sake of not breaking things, and forces you to use a third party library anyways (at least it's my experience with Python and exactly the reason why PHP is a mess).

IMHO Node.js not being "batteries included" is for the best.

Re:Pushing the performance limits of Node.js by betenoire on Thursday August 27, 2015 @06:19PM (#10132521)
that's true. in my memory, it was that way with php 15 years ago too, thinking of phpclasses.org, hotscripts.com etc. Always sorting through the trash...