Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>Node.js bases everything around async programming, and this is just too difficult for mediocre programmers to wrap their heads around, and use effectively. (But it's fantastic for good programmers.)

It has nothing to do with mediocre vs good programmers.

A good programmer maybe better able to hold an async callback flow in his mind than a mediocre one, but he too will be hampered by it. I.e both will be MORE productive with non-callback async style programming. Callback style async code is needlessly more difficult compared to linear style async code --and the keyword here is "needlessly", as this difficulty doesn't buy you absolutely nothing, only introduces more bugs and hampers readability.

(To clear another misconception, it also shares very little with event-driven UI code --there the callbacks are much more coarse, based on high level tasks).

Guido, the creator of Python, a good programmer if I ever seen one, absolutely abhors async programming. And the designers in all modern languages, from C# to Go to Scala to Erlang etc, have also decided against using the Node style for async programming.

Plus, it's not like Ryan Dahl is some programming of Dennis Richie proportions, or anything like it either. Compared to most language designers, he is just a script kiddie. Considering, also, that node isn't even a language, it's a hack on V8, similar to what dozens of people have already done on other platforms, from Tornado to Twister, to EventMachine etc.




Which is why they scrapped it and introduced async and friends:

http://blogs.msdn.com/b/csharpfaq/archive/2010/10/28/async.a...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: