Monolithic Node.js • Hacker News Board

Re: Monolithic Node.js

#21

Post by Stwerner » Mon, Dec 16, 2013, 9:58 PM UTC

The seneca toolkit that the post leads into and links to is super interesting. It seems like a pretty straightforward way to build with an SOA from the beginning. Does anyone have any experience using this for a sizable project that can comment on it?

Re: Monolithic Node.js

#22

Post by secoif » Tue, Dec 17, 2013, 8:12 AM UTC

coldtea wrote: post #9

secoif wrote: post #4

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

Which tells us more about you than about the post.

huh?

Re: Monolithic Node.js

#23

Post by collyw » Tue, Dec 17, 2013, 2:50 PM UTC

_random_ wrote: post #19

zzzeek wrote: post #11

this post rolls out every OOP canard there is. OOP implies monolithic design; OOP models the world in a naive and impractical way (but functions and callbacks are clearly just fine, obviously); OOP implies you'll have to "roll out" GOF (implying GOF is a "cookbook"; anyone who read it and understood it knows that this is absolutely not what was intended); "design patterns" are a code smell; only OOP has "design patte…

Many people don't want to care about types and correctness, they just want to be able to hack quickly in dynamic/weak languages. Future maintenance is someone else's responsibility,

You can write shitty unmaintainable code in a statically typed language, and maintainable elegant code in a dynamically typed language.