3 ms·

Maybe I need a refill of coffee, but I couldn't really grasp what the point of the article was. JavaScript is half-usable, object oriented programming is broken

Maybe I need a refill of coffee, but I couldn't really grasp what the point of the article was. JavaScript is half-usable, object oriented programming is broken (he even goes into a bit about inheritance), Java and .Net are enterprise-ready languages...huh?

untog 13y ago
The article seems to be refuting assertions that Node is no good for enterprise, but without calling out specific articles that do so. So it's a little difficult to get. It's also a response that says "Node is no good for enterprise because enterprise development is broken", which isn't wrong, but doesn't necessarily help much. Changing the coding practises of every developer you have is not a small problem.
ebiester 13y ago
The point is that node.js is a classic case of "worse is better." That is, because of its lack of namespacing, NPM came up with a great module system that made modular programming the default, making code cleaner. Its limitations forced smart architecture. I don't know that I agree, per se, but that piece of the argument is interesting.
plorkyeran 13y ago
It's awfully rambling. I think the high-level idea is that you can't build large monolithic applications in Node, but that's not actually a problem because building large monolithic applications doesn't work very well in any language, and Node is unusually good at building modular applications.
coldtea 13y ago
Get your coffee and read it again. He explains his point rather well, and it's about the difficulty of bulding large codebases with big teams in JS and some ways to overcome it.
scriptproof 13y ago
I believe the point is in the conclusion and the content leads to the conclusion: If you change your mind, you may start to see the advantages of Node, that is not possible if you continue to think with older models in mind.

3 ms·

Maybe I need a refill of coffee, but I couldn't really grasp what the point of the article was. JavaScript is half-usable, object oriented programming is broken

by rmrfrmrf 13y ago

untog 13y ago
The article seems to be refuting assertions that Node is no good for enterprise, but without calling out specific articles that do so. So it's a little difficult to get. It's also a response that says "Node is no good for enterprise because enterprise development is broken", which isn't wrong, but doesn't necessarily help much. Changing the coding practises of every developer you have is not a small problem.
ebiester 13y ago
The point is that node.js is a classic case of "worse is better." That is, because of its lack of namespacing, NPM came up with a great module system that made modular programming the default, making code cleaner. Its limitations forced smart architecture. I don't know that I agree, per se, but that piece of the argument is interesting.
plorkyeran 13y ago
It's awfully rambling. I think the high-level idea is that you can't build large monolithic applications in Node, but that's not actually a problem because building large monolithic applications doesn't work very well in any language, and Node is unusually good at building modular applications.
coldtea 13y ago
Get your coffee and read it again. He explains his point rather well, and it's about the difficulty of bulding large codebases with big teams in JS and some ways to overcome it.
scriptproof 13y ago
I believe the point is in the conclusion and the content leads to the conclusion: If you change your mind, you may start to see the advantages of Node, that is not possible if you continue to think with older models in mind.