Monolithic Node.js

#1

Post by medeu » Mon, Dec 16, 2013, 5:37 PM UTC

Re: Monolithic Node.js

#2

Post by rmrfrmrf » Mon, Dec 16, 2013, 6:15 PM UTC

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?

Re: Monolithic Node.js

#3

Post by schmichael » Mon, Dec 16, 2013, 6:20 PM UTC

The section on why objects are bad is awful. It appears the author is describing C++/Java/C#'s class based object orientation, which is definitely open to critique, but it's so poorly worded and vague I end up feeling the author doesn't know what he's talking about.

Re: Monolithic Node.js

#4

Post by secoif » Mon, Dec 16, 2013, 6:34 PM UTC

This is the longest blog post I've ever read.

Re: Monolithic Node.js

#5

Post by untog » Mon, Dec 16, 2013, 6:34 PM UTC

rmrfrmrf wrote: post #2

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?

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.

Re: Monolithic Node.js

#6

Post by ebiester » Mon, Dec 16, 2013, 6:35 PM UTC

rmrfrmrf wrote: post #2

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?

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.

Re: Monolithic Node.js

#7

Post by plorkyeran » Mon, Dec 16, 2013, 6:37 PM UTC

rmrfrmrf wrote: post #2

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?

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.

Re: Monolithic Node.js

#8

Post by coldtea » Mon, Dec 16, 2013, 6:38 PM UTC

rmrfrmrf wrote: post #2

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?

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.

Re: Monolithic Node.js

#9

Post by coldtea » Mon, Dec 16, 2013, 6:39 PM UTC

secoif wrote: post #4

This is the longest blog post I've ever read.

Which tells us more about you than about the post.

Re: Monolithic Node.js

#10

Post by scriptproof » Mon, Dec 16, 2013, 6:40 PM UTC

rmrfrmrf wrote: post #2

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?

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.