News for hackers. Stuff that matters.
Re:What the web platform can learn from Node.js: The Darwini... by phillmv on Wednesday December 16, 2015 @01:48PM (#10746294)
I've heard this claim before and it feels like a mixture of stockholm syndrome and wishful thinking.

In my experience, it's a bit of a shit show. You end up with libraries that are subtly incompatible, or have overlapping functionality, or strangely large holes of functionality that require overlapping combos of libraries and therefore nobody's written.

If you get your socks off writing shims and glue and maintaining it against a thousand moving targets, power to you.

In my opinion, what you really want is someone to bundle composable libraries for you. That bundling has incredible value. You know that everything more or less works, in ways that you'd expect, because someone else managed to test it.

You have all the functionality basics down pat. The shims you do have to write work at higher levels of abstraction. Etc, etc.

Re:What the web platform can learn from Node.js: The Darwini... by Swizec on Wednesday December 16, 2015 @02:09PM (#10746447)
> In my opinion, what you really want is someone to bundle composable libraries for you. That bundling has incredible value. You know that everything more or less works, in ways that you'd expect, because someone else managed to test it.

Sooooo a big monolithic framework like Rails or Django? I thought we said those are bad.

Re:What the web platform can learn from Node.js: The Darwini... by woah on Wednesday December 16, 2015 @02:22PM (#10746554)
I think that at this point we can conclude that monolithic frameworks and minimal modules are BOTH bad. Software development is bad.