Echo JS 0.11.0

Though it takes a single chain of inside-jokes to go from full elegant to reddit, as in:

I really had to say that I agree with the comment you agreed in what you had to say.

(Forgive me for this, won't happen again =) )

I was so close to getting into top 10. Damn! =)

Lack of a friendly clip is what kept me from making user "friendly" web sites all those years! =)

This is really great btw.

I don't want to sound negative but, Angular already feels bloated. Is this really worth the complexity it brings? (I'm really asking. Like, do you really have a significant improvement on your productivity?)

I had down-voted the article about performance-tests because, well we have enough comments under it. But this... This is a new release. I also don't get it.

That may not have been clear: By publishing test code, I mean, sharing all the details about running that snippet as well. For instance, Vert.x has a lot of configuration options which affect its performance significantly.

Down-voted. Please publish the test code and even better, make a pull request to the techempower benchmarks ( http://www.techempower.com/benchmarks/ ) github repo ( https://github.com/TechEmpower/FrameworkBenchmarks ) to be included in there.

@pokani I'm simply pointing to the fact that the whole node ecosystem is built by assuming that node is single-threaded. When multiple threads are necessary, most people write it as a native extension and provide a callback to the JS world. I'm not discouraging you or anything. I love innovation. I just want to understand how this helps me. I see, that one may start pushing blocking operations to other threads, but doesn't it make sense to do such operations on a lower level anyway? I also think that this fork is too tied to a web framework.

Node.js supports c++ plugins. Unless you make it clear exactly why you needed a fork of it instead of a plugin, people will get confused. JavaScript is designed to be single threaded. The implementation may run async functions on other threads but programmers usually have no option to force spawn threads. If you need to spawn threads, write a native extension which does. I understand it may have taken a lot of work and I really appreciate the effort but we don't have any information about the real purpose of this (what can we do now that we previously couldn't?)

First of all, a question: I didn't see an obvious way to interrupt and check for permissions when clients make a request. Method validations look good but where do I get the session to check?

Well, other than this, it really looks great. Looking forward to further development. Best luck to the author.