On Mon, Apr 2, 2012 at 6:53 PM, TipTop <[email protected]> wrote:
> So I would like to know where node thinks it will be in 1 year? > > What are things that are been looked at for improvement with node as a > whole? > > At some point nodes going to run into a wall, and that wall is javascript. > I feel that js is nodes achilles heel. I LOVE js and live by it but its has > flaws, maths and stuff like that. > At that point, just like Rails did with Ruby, you need to extend the language by coding C++ modules and wrappers to improve performance where needed, or isolate calculation heavy parts of your solution and spin them out in separate technologies. At that point, when you are building a "for reals" application on the interwebz, you need to start thinking of your app as a conjunction of services and not of a standalone one-size-fits all cluster. Which is really part of what the node.js "revolution" is about - making smaller apps that fit together well in a unified, event-driven whole. > Whats the plan? > Continue kicking ass? > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
