Your statement is an incredible generalization of a large group of developers. It may be your experience, but I have to counter it with my own. While the Windo

Your statement is an incredible generalization of a large group of developers. It may be your experience, but I have to counter it with my own. While the Windows/.NET stacks may not provide as many pre-built solutions to handle 'big data' (a term I'm growing to hate), I have worked with tons of competent developers who have been able to build solutions to answer exactly the kinds of questions you propose. I've seen it done with SQL Server Reporting Services, Analysis Services and even straight custom C# code. I've seen it done with Hadoop + streaming API, StreamInsight (CEP rather than post processing) and custom Workflows in WF. As for your other statements that are just built to jump on the 'hate Microsoft' bandwagon, just because a single large company doesn't iterate fast enough to keep up with the rest of the OSS landscape doesn't mean that .NET didn't have options available to it. Nancy provides great REST capabilities and has existed since 2010. Devs were building REST services with Microsoft's ASP.NET MVC during the same period. Others were using WCF REST (not great, but usable) at the same point as well. WCF Data Services was another option. ORMs.. Theres the ever-expanding Entity Framework (which I don't love), NHibernate and many many others. Lets not just jump in and bash MS because you've only worked with bad developers using their stuff.