Re: Node Modules or Sub Apps (Was: Hosting a Large Number of Node Apps on the IBM i)

I've been mostly trying to stay out of the debate though have been watching
it. A couple comments:

1 - The internet has never known the amount of workload the likes of
Netflix/LinkedIn/Walmart/etc are processing. Easy for us to sit back with
our 1/10000th of a work load and say the technology/approach is junk.

2 - Each of these shops didn't start out with Node.js and instead moved to
Node.js from something else. I think Walmart said they liked Java/Servlets
but couldn't develop in it fast enough. They more features faster because
of Amazon.

3 - The sheer amount of open source can become unwieldy. That's why the
community started creating things like ruby-toolbox.com to convey stats
about open source categories (i.e. ORM) to lessen the amount of time a
programmer needs to spend researching options. In short, this is
aggregation at its best.

​4 - Jade/haml/<insert other html-lessening technology> are great tools for
creating more whitespace in the view layer code. Less for my eyes to
consume means faster to maintain (for me anyways).

​5 - EGL had(has?) phenomenal technology that I don't know if it has been
accomplished well in other stacks.​ For example, front-end to back-end
line-by-line visual debugger. IBM screwed up and thought it could
manufacture a language and bring it to popularity. They've since learned
you need to buy your way into existing popularity (i.e. purchase of
StrongLoop - a big Node.js player).

6 - Neils, keep pursuing Javascript on JVM and let us know how it goes.
I've also gotten Scala working though haven't developed anything of
significance yet.



Aaron Bartell
litmis.com - Services for open source on IBM i