Starting a new thread to get answers to the persisting question: What are the best use cases for node.js project?
Ben Noordhui's following response (for "Ideas for contribution to node.js in the context of a Master's Thesis") and few other responses to user's specific use cases, generally caution the users against node's abilities*:* * * > There are some things you cannot reasonably do in node.js no matter > how hard you try, things like hard real-time, complex math, etc. They're > fundamentally at odds with the language and the environment it runs in. > Then there is the broad category of things you /can/ but not necessarily > /should/ do. CRUD web apps come to mind: you /can/ write your new blog > engine in node.js but it doesn't have a killer edge over other languages or > frameworks (except for client/server code sharing, maybe.) If you are starting a new project and have a partial and a high level sense of the application's underlying architecture. And, if you are trying to be agile, then you want to get started and evolve as you go rather than wait until the complete spec is done and scoped. What highlevel architectural themes or features are best suited for node and what are not. If you have started with node and moved to something (and if you are still on the list) or if you transitioned from something to node your use cases and experiences will be of value. Thanks -- 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
