*The real question is why wouldn't you want a piece of that?* * * As an enterprise monkey, I can see that most people don't - they want to drag and drop some web services onto a form control and if it doesn't work, find somebody who knows more about framework 'x' to spend time debugging it.
That makes it not appropriate for most enterprise environments unless you've got the manpower to take it on, and are planning on getting rid of the monkeys by either training them not to be monkeys or or by firing them :-) On Wed, Jul 4, 2012 at 10:34 AM, Richard Marr <[email protected]>wrote: > > In my experience performance is rarely a language/platform issue, and > rarely the deciding factor when choosing tools unless you're working on > high frequency trading systems (which you aren't because you wouldn't be > using ASP.NET). > > We live in an economy of ideas, where you should spread the widest net you > can. Node.js has one of the most vibrant and varied communities around, and > is engaging head-on with a new and interesting way of tackling > software. The real question is why wouldn't you want a piece of that? > > > > On 3 July 2012 18:56, Justin Collum <[email protected]> wrote: > >> Had a discussion with a friend about Nodejs the other day. We are both >> C# / MVC / ASP.NET devs, with about 10 years experience. He asked me why >> someone would choose Nodejs over IIS + MVC . My argument was 1) >> performance 2) non-blocking IO. Keep in mind that I don't know a lot about >> node, I've built one small site and that's it. So my argument in favor was >> pretty short. >> >> His response: Well, if I need performance on IIS I can just bump up the >> number of threads in the thread pool. Fair point. >> >> After looking into it a bit, it seems that the big difference between >> IIS + MVC and Node is that each thread can do more in the Node world >> because of the non-blocking IO. This cuts down on context switching and >> makes for better overall performance. Add that to the "one language to rule >> them all: coffeescript" factor and it's a clear win to me. >> >> Is that a fair summary of the performance advantages of Nodejs over IIS >> + MVC? Is there more to it? >> >> I'm aware that you can run Nodejs via IIS but my intuition tells me that >> won't be a good fit. >> >> -- >> 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 >> > > > > -- > Richard Marr > > -- > 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
