crueber

If you truly need to do sync programming for whatever reason, you probably aren't using the right language. It's not just web programming that benefits from asynchrony, it's pretty much any non-trivial algorithm. Sure, it can require a bit more code to do right, but you don't want to block all your other background events from firing just because you have to write a bit more code.

If you really prefer synchronous style, and don't mind the drawbacks, there are plenty of languages out there that'll work better for you. PHP, Ruby, and Python readily come to mind.

Hogwash. It seems like this person doesn't understand that node is an event based, asynchronous language, and that's one of its big advantages over other languages that force threads, or don't generally offer parallel execution.

If this had compared Node.js with clustering and async vs a synchronous language like Ruby, it might have been interesting. Maybe. But non-asynchronous operations in Node are an antipattern that core node contribs are trying to remove (the -Sync in node stdlib are trying to be removed).

Good coding conventions, promises, generators, and async/await are your friends for making callback hell go away.

You are running a circular argument. What determines stability for a programming language. Running code? I've got plenty of that. Not crashing? I've seen no more crashes on 1.1 of io.js than I have on 0.10 of node, which I also consider to be perfectly stable for production applications, as I run several. So I say again, for what values of stable? Failing tests only indicate a change. Is something broken for you?

Please cite your io.js source for their statement of maintaining 100% compatibility with all node modules. I can't find any reference to that anywhere. NPM is certainly usable, as I use it daily with io.js, which fits their websites statement of "This project began as a fork of Joyent's Node.js™ and is compatible with the npm ecosystem.".

Still nothing credible in this thread, move along.

I don't see a single factual statement here.

io.js spent part of December in a rapid incubation, and released in early January.

It's stable for me on several production applications, but what does 'stable' actually mean, vs 'beta'.

Their community started open, and remains open, and has a larger contributing base than node by more than triple. They have an open technical committee, with meetings that anyone can attending (and I have).

Here's the spade: You're wrong. Actually do your research, have facts that you can back up, and try again. Your tune will be very different when you have the facts.