Evolving the Node.js Brand

Re:Evolving the Node.js Brand by jerf on Monday July 11, 2011 @01:50PM (#2751704)

Since it seems to run contrary to what others are saying, I like the hex-inspired logo. It's much more distinct.

The graph is an actively-bad idea both visually and philosophically, unless they're really deeply committed to making Node actually work like that. It looks like it is claiming to support lots of internode cluster-type communication; as I understand it, it has no story except vague sketches here, and no matter what it will be a long time before that is the primary story Node has. There's a long row to hoe betwixt here and there.

[ Parent | on HN ]

Re:Evolving the Node.js Brand by IsaacSchlueter on Monday July 11, 2011 @04:46PM (#2752448)

> It looks like it is claiming to support lots of internode cluster-type communication

There are a few projects that specifically take advantage of node's ability to proxy and distribute work across multiple processes.

Check out these projects:

http://learnboost.github.com/cluster/

https://github.com/nodejitsu/node-http-proxy

https://github.com/substack/dnode

Or my very early prototype botnet thingie: https://github.com/isaacs/sodn

[ Parent | on HN ]

Re:Evolving the Node.js Brand by jerf on Monday July 11, 2011 @04:53PM (#2752478)

Node has no special ability to proxy and distribute work across multiple processes. Erlang, Hadoop, OpenMPI, those are things with special abilities to distribute work across processes. "Being able to use sockets" is not a "special ability", not even if you add the word "asynchronously". I'm not aware of a language environment of any significance now where you can't use "asynchronous" sockets. You are trying to build an ability, not harness something that already exists. There's nothing wrong with that, but it's a bit premature to put something like that right in the logo.

[ Parent | on HN ]