> So I would like to know where node thinks it will be in 1 year? Well, node core, I think, is in a place where it's starting to converge on an intended final state. You won't see any sweeping api changes probably, and instead will see improvement in the user experience and a lot of stability fixes. In a year, node will be that much more battle-hardened but not really fundamentally different.
All the action's gonna be in userspace, I think. First of all, I think we're going to see improvements on the "browsing npm" front, since they're sorely needed and something people are already experimenting with. I also think we're going to see a change/solidification in terms of common node.js frameworks. Right now express is still really popular but there are many new frameworks coming out (there was a podcast about these frameworks on nodeUp not too long ago) and I think at least a few of them are going to give express a run for their money. Speaking of money: Mine's on flatiron, but hey, I'm biased. With improvements on the native bindings experience, I hope we also see some interesting new native bindings, though current trends indicate people prefer pure js bindings for reasons other than "oh maan I have to compile something" imo. > At some point nodes going to run into a wall, and that wall is javascript. I will admit that javascript has its limits (numerical stuffs as you point out). However, I don't think these will be experienced as a wall. Instead, I predict that other environments and languages will get libuv bindings (along the lines of luvit), and that for certain problems these will become popular. For example, I saw a branch on julia-lang for binding the core to libuv, and that would be a great way to create services that can data crunch. On a similar note, luvit is already being used in places where v8 has been deemed to have too large of a memory footprint. Cheers, --Josh On Mon, Apr 2, 2012 at 4:09 PM, Mark Hahn <[email protected]> wrote: >> At some point nodes going to run into a wall, and that wall is >> javascript. > > In what way is javascript limiting? > > -- > 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 -- Joshua Holbrook Engineer Nodejitsu Inc. [email protected] -- 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
