Node.js is Backwards

Re:Node.js is Backwards by akdubya on Tuesday June 14, 2011 @01:27AM (#2651888)

I'm working on a distributed app that shares code between the client and server, and there are already a multitude of open-source libraries that are designed to run in any JS environment.

[ Parent | on HN ]

Re:Node.js is Backwards by jessedhillon on Tuesday June 14, 2011 @03:03AM (#2652070)

That doesn't mean it's useful to do so, or that there are significant advantages to be gained from doing so.

[ Parent | on HN ]

Re:Node.js is Backwards by ricardobeat on Tuesday June 14, 2011 @08:59AM (#2652762)

Like, say, sharing hashing functions, templating, encoding or math libraries? Not useful at all.

[ Parent | on HN ]

Re:Node.js is Backwards by jessedhillon on Wednesday June 15, 2011 @04:42PM (#2658939)

Actually yeah, that doesn't sound very useful.

Math (significant math), encoding and hashing being done on the client sounds like a poorly designed application. Same for templating on the server -- which I assume you mean manually compiling templates using a library, and sending the result to a client, perhaps as a property of a JSON object.

[ Parent | on HN ]

Re:Node.js is Backwards by alnayyir on Tuesday June 14, 2011 @03:12AM (#2652083)

This.

Also I appreciate you picking up where I left off, I've been making a major lifestyle change and am almost completely sapped of energy.

This has improved my concision considerably wrt code and conversation.

Cheers, let me know if you find yourself in SF, I'll get you a round on me.

[ Parent | on HN ]