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

The proposal acknowledges that the current JS/V8 cannot really deliver on the original promise that all IO should be async. This is mainly because of awkward syntax in JS. The awkward syntax comes from the lack of native futures.

Where does the proposal acknowledge this? This discussion is about different styles of evented async programming, e.g. Promises vs pure function callbacks. What awkward syntax do you mean?

If that's the path they chose, what will distinguish Node from high performance network libraries in other languages, such as EventMachine and Twisted?

The main thing distinguishing Node from these frameworks is JavaScript's easy anonymous functions for easy asynchronous callbacks.

Node has it's reputation for speed precisely because it doesn't offer any blocking operations.

Node does offer blocking operations e.g. on the file system. I use them once when the program starts up to read configuration data. It's not going to cause problems unless you're doing blocking IO on every connection.

Node has a reputation for being able to scale to thousands of connections due to its evented nature - not a reputation for speed.



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

Search: