Consider how different a task that is. Each of these benchmarks and frameworks are run on Linux, which means the turn-up and benchmarking automation all target Linux. Including a new framework involves creating a new stack (app/web/db server) and app that meets the criteria. Including Windows would require Windows versions of large parts of the toolchain.
I suspect that the most significant reason has to do with fragmentation in knowledge. Linux is a huge knowledge domain. Windows is also a huge knowledge domain. It's rare to find people (or even teams) that are well versed enough in both to deliver meaningful results on both.
My understanding is that there are ASP.NET community members stepping up to help bring ASP.NET benchmarks to the table for the next round.
There are significant restrictions as far as what benchmarks from the .Net framework are allowed to be publicly published. Not sure if this has anything to do with why this project hasnt included ASP .Net
Simple really. Its heritage is single-user desktops. Therefore the security model is often "Don't look in here!" rather than having it done right the first time. Hides filenames; needs antivirus.
Industry standard network/admin/deployment tools don't work as well, if supported. Until a couple of years ago, the only viable way to manage it was from a GUI... they are still figuring out how to run it headless. It's not always compatible with open standards. Shall I continue?
Meanwhile Unix (and others) began life as time-sharing systems that became the original nodes of the internet, a scalable model that Windows has come back to forty years later. That's not to say that it doesn't have any strengths or isn't improving.
The extra cost includes per minute charges on EC2.
That's great except the only thing you've proven here is your own ignorance. Shall I go on?
You're spouting off about ancient history...and that somehow translates to Windows is (currently) "clumsy" on the network? Gee, I wonder why it only takes me 10 minutes flat to setup a headless ASP.Net server on EC2? And I can do that even with the GUI version of Windows because there's this little thing called RDP - maybe you've heard of it.
Oh and ASP.Net also runs on Linux. It didn't a few years ago though, so maybe it won't work for you since apparently you are living in the past.
(Forgot to mention drive letters, unc paths don't work on the console.)
rdp is no substitute for real deployment tools. That you've spent years working around the issues and recently got headless working seven months ago is not impressive. Not when its been mature elsewhere for decades, for free. Nor is your defensive tone.
The original point I made was that there are impediments to using Windows and many still exist whether you believe them or not. If they didn't Windows Server wouldn't be moving closer to the Unix model with every release.
