Matt, I'm not offended by the tone. I understand the intent and tone are hard to convey on the internet. That's why I love going to tech conferences to meet people face to face. I hope to be at nodeconf this summer, maybe we can discuss this there.
But I do disagree with your statement "it's just that people need to understand that Node will never be the high performance static file server that nginx is. And trying to get there seems pretty futile to me". I can see that you're just trying to do your civic duty and make sure people know that serving static files isn't something node is good for. I personally think it can be good for that. If it helps any, my role in the node community is and has always been a mix of helping people learn the basics while at same time pushing node to do things it wasn't meant to do. Even if node never becomes as good as nginx at what nginx is good at, it's a good experience to try and node will be better off for the attempt. I've tried a lot of crazy things with node including desktop gui apps, desktop games, webgl on tablets (yes node, not webkit), and I serve all my static sites with node. It's plenty fast and stable for my needs so I don't bother with throwing nginx in front of it. I know how to configure nginx and have done some pretty advanced stuff with it, but why use an extra layer I don't need. -Tim On Tue, Feb 14, 2012 at 9:38 AM, Matt <[email protected]> wrote: > On Tue, Feb 14, 2012 at 8:49 AM, billywhizz <[email protected]> wrote: > >> Matt - there's no need to be so rude, especially to one of the best >> guys in the community. >> > > I didn't mean "benchmarks or GTFO" in any rude way - it's just that people > need to understand that Node will never be the high performance static file > server that nginx is. And trying to get there seems pretty futile to me - > the web is GREAT at small pluggable components - so use it like that. Stick > nginx up front, haproxy in front of that if you need it, and node in the > backend doing your dynamic content. This design has HUGE advantages over > just using Node for everything, and it's simple to manage and run. > > >> getting close to nginx performance is >> definitely achievable >> > > Like I said, let's see some benchmarks then. I just really doubt you'll > get all that close in any sane flexible manner supporting all the correct > headers (eTags, If-Modified-Since, etc). There's value in having both node > and nginx in your architecture. > > Matt. > > -- > 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
