Live data from Hacker News

Getting out of your comfort zone with Node.js

blog.count.ly

1–10 of 14 posts

Re: Getting out of your comfort zone with Node.js

#3
We were used to building stuff in static, strongly typed languages. We had powerful IDE support, stable libraries, old and proven frameworks. There was always the right tool, the right library, the right idiom, the right way.

There was confidence and security in the well known world of stuff you already tried and built. The confidence that came from the knowledge of how difficult or easy something could be. The skill of estimation was fine tuned, and the feeling for effort was strong.

It was not the fact that nothing could go wrong that was comforting. It was the power to know what, when and where could go wrong.

An anxiety-neutral condition, with limited set of behaviors to deliver a steady level of performance, usually without a sense of risk.

A true comfort zone.

Then we chose Node.js for a project. We are yet to see how wise a decision that was business wise, but it was certainly good for the soul.

Re: Getting out of your comfort zone with Node.js

#6
post #4

tl;dr: we tried something new, namely node.js. We liked it. You too should try something new from time to time. What's newsworthy about this post, beyond being positive to a project that everyone seems to like (including me)?

Adding to

  if buzzword_count['node.js'] > x: required_qualification_keywords.append('node.js')

Re: Getting out of your comfort zone with Node.js

#7
post #4

tl;dr: we tried something new, namely node.js. We liked it. You too should try something new from time to time. What's newsworthy about this post, beyond being positive to a project that everyone seems to like (including me)?

Because occasionally posts tend to focus around people defending their well worn, trusty tools against these new upstarts.

Re: Getting out of your comfort zone with Node.js

#8
post #4

tl;dr: we tried something new, namely node.js. We liked it. You too should try something new from time to time. What's newsworthy about this post, beyond being positive to a project that everyone seems to like (including me)?

Thank you. The article was not easy to scan quickly - too few paragraphs.

Re: Getting out of your comfort zone with Node.js

#9
I am so tired of reading complaints about PHP performance only to realize that the author uses some bloated, over-engineered framework like Cake or (much worse) library like Smarty. What do you expect?

Yes, high-level design matters. Ever since I switched to my own framework in 2005, most of the pages on my websites generate in less than .1 second, and that's without extensive caching, often on cheap VPS. There is nothing fancy about it, just simple, straightforward system design that doesn't fight the language and pretend like I'm coding Java.

Re: Getting out of your comfort zone with Node.js

#10
post #5

I've rewritten entire python codebase of my company in node.js several weeks ago. I like the 'purity' of it all now. It irks me still that js isn't really comforting at actual scripting.

That's a real pity. You probably would have been hugely better off with gevent instead. Using gevent isn't quite as good as using a language with a true preemptive runtime, but it's way easier to work with than nested callback spaghetti.

Anyone else considering Python -> Node, look very carefully at gevent first. Not only can you save the rewrite, you can end up with a better solution at the end too.

http://www.gevent.org/

Post reply on HN