To boldly go where Node man has gone before

Re:To boldly go where Node man has gone before by moocow01 on Wednesday May 16, 2012 @05:02PM (#3984000)

If there is one thing I've learned its to ignore benchmark tests on relatively established technologies.

You'll drive yourself into the looney bin if you hop from one thing to the next based on these comparisons that inevitably popup every month or so.

If you enjoy programming in JS with Node use it - if you enjoy programming with Go use it. Your enjoyment will far outweigh performance differences that will be minor in 99% of real world cases.

[ Parent | on HN ]

Re:To boldly go where Node man has gone before by guscost on Wednesday May 16, 2012 @09:43PM (#3984948)

I use Express, because I can make and host a fast web page in 3 minutes, and if I ever come across those fabled unsolvable "scaling problems" I can abandon whatever needs to be rewritten without a second thought. Admittedly this is usually for promotional media and assorted small projects, but it still works great.

[ Parent | on HN ]

Re:To boldly go where Node man has gone before by IsaacSchlueter on Wednesday May 16, 2012 @05:08PM (#3984020)

Yes, exactly.

[ Parent | on HN ]

Re:To boldly go where Node man has gone before by taligent on Wednesday May 16, 2012 @06:03PM (#3984283)

Also it is often external influences that will drive performance improvements e.g. Nginx, Redis, Memcached, Javascript caching etc.

[ Parent | on HN ]