About PayPal's Node vs Java “fight”

Re:About PayPal's Node vs Java “fight” by mattgreenrocks on Saturday December 14, 2013 @08:39AM (#6905644)

Do you know of any shops that use Uncle Bob's approach (besides 8th Light, of course)? I don't; I wish I did. I agree that isn't something you'd use every time, but I feel there isn't a whole lot of data out there when people have used it. All I see online are devs whining about the extra work.

I don't know what it is about the web, but it's as if we decided all of software architecture didn't mean anything and threw it out. My theory: it's harder to feel coupling in a dynamic language, thus it's just an academic concern!

[ Parent | on HN ]

Re:About PayPal's Node vs Java “fight” by ebiester on Sunday December 15, 2013 @12:44AM (#6908518)

I have plans to try it in a side project. I too am skeptical about the rewards of setting up a CRUD system like that.

It isn't that we've decided that software architecture meant nothing; rather, we settled on one architecture that is Good Enough. The View/Controller/Domain paradigm of Rails works for many projects.

[ Parent | on HN ]

Re:About PayPal's Node vs Java “fight” by mattgreenrocks on Monday December 16, 2013 @01:34PM (#6916783)

It won't be great for CRUD. It's really meant for applications that have a bunch of business logic to them...you know, the interesting apps.

Aside: "good enough" seems to summarize the web as a whole. This is both discouraging and a fact of life.

[ Parent | on HN ]

Re:About PayPal's Node vs Java “fight” by ebiester on Monday December 16, 2013 @05:02PM (#6918143)

You can still have an interesting business logic system that is CRUD at its core. A case management system, as an example, is CRUD at its basis but filled with business logic.

[ Parent | on HN ]