I worked on improving the aspnet (on Windows) results and I committed aspnet-stripped (based on @pdonald's aspnet tests) and HttpListener.

As that committer, I have to ask: Why would you change your career path due to supposed 'abysmal performance' reported on a website?

Keep in mind that the 'abysmal performance' of many of the frameworks can still handle millions of requests per day. Plus, many of the 'slower' frameworks have other development benefits like ease of development, community ecosystem, static type checking, etc.

The reason I replied is because I'm considering jumping from aspnet to a 'slower' framework like django and I'm not basing my decisions solely on the results of this collaborative benchmark where I don't even know if experts have tuned the results, and where I don't know why the results are 'poor'.

> I'm considering jumping from aspnet to a 'slower' framework like django and I'm not basing my decisions solely on the results of this collaborative benchmark

I'm not basing my decision solely on these benchmarks either, this is just the straw that broke the camel's back. Microsoft doesn't inspire me too much confidence on the future of .NET and neither does Mono. The .NET open source community has never taken off. And changing my main development language is not such a big deal, I already work with five languages on a regular basis.

I hope to see better results on future tests. I hope OWIN improves the situation for ASP.NET. And I hope future versions of Mono focus more on performance. But that's a lot to hope for and I'm not holding my breath.

You can actually know that experts often haven't tuned the results because many PRs are being ignored ever since the beginning of this project. There is a pretty clear agenda.

Say what? Which of these [1] is old and being ignored?

[1] https://github.com/TechEmpower/FrameworkBenchmarks/pulls

Thanks, Sker. I really appreciate your kind words. We're not dissuaded at all! I figured I wanted to catalog my thoughts in response to questions about unfair comparisons into a single place. To be clear: I don't slight people for having strong opinions about right and wrong in web development. I just ask them to realize there are varied points of view, including many who have enjoyed looking at the totality of data.

We've been really busy of late, so we still don't have an ETA for Round 7, but believe me that we are very eager to get that completed. One thing we're hoping to include in Round 7 is Windows on physical hardware.

Also, just another aside, some folks might hate the background animation. You can turn it off at the bottom right. Consider it my trolling you if you must. :)

You can write perfectly performant apps in most languages. The problem is often the communities that surround them. Node.js has some nice advantages but I wouldn't compare by performance next to C# and Java. I'd compare on community, language philosophy and typical code quality. Java and C# and the median developer level are awful.

This should be formalized into some kind of internet geekery law.

> X Nazis will complain about any X, no matter what. Don't let them dissuade you from continuing work on X.

I love contrarianism and geekery, just don't get lost in the infinite correctness maze.