Aaron Stannard, a .NET developer and Akka.NET co-founder, writes on the .NET open source ecosystem, startups, and developer skill.
HN links it in debates over why .NET lags among startups and how Microsoft shapes the .NET open source ecosystem.
Aphyr has thoroughly explained what is wrong with MongoDB[1]. I'm quite sure that things aren't probably as swell with your tech stack you might imagine. A commenter here has in the past demonstrated how to cause someone using MongoDB data problems by sending too much information too quickly for MongoDB to handle in a targeted way although I can't find the link to it now. I have been wanting to try it myself to see if I could do it too. Firebase uses MongoDB[2]:
"Firebase stores all its data in MongoDB which offers the built-in capability for apps to scale automatically and gives each piece of data its own unique URL stored in JSON documents."
I was going to see if I can get achieve data consistency problems there for my own firebase app.
Also posts that malign MongoDB frequently make it to the home page [3][4].
[1] http://aphyr.com/posts/284-call-me-maybe-mongodb
[2] http://www.mongodb.org/about/production-deployments/
[3] http://www.sarahmei.com/blog/2013/11/11/why-you-should-never-use-mongodb/
[4] http://www.aaronstannard.com/post/2013/12/19/The-Taxonomy-of-Terrible-Programmers.aspx
The issue here was Microsoft appointing itself judge and jury of which projects should have most-favored-nation status and that criteria being reflected directly into the package distribution system. Given Microsoft's singular influence over the .NET ecosystem, this presents a massive conflict of interest especially when pitting Microsoft's own first party solutions versus third party ones - there would be a tremendous amount of pressure to ensure that the MSFT packages rise to the top of the ladder without any guarantee as to their longevity.
I detailed this all at length here prior to defeating the initiative: https://aaronstannard.com/dotnet-foundation-maturity-ladder/
I stumbled upon a post today on Voat's scalability:
http://www.aaronstannard.com/voat-scalability/
This is the key issue it seems:
>As for the SignalR issues, I was able to confirm that Voat is running on a single box. Not a big deal given that it's still a hobby project for the developers, but the fact that it's not designed to run on anything other than a single box is an obvious problem. Either remove SignalR or support a backplane for it.
The community has begun contributing to microsoft-sactioned projects (notice those projects listed are all ms initiatives). There is still weakness in community initiaited/run projects, 2 years later http://www.aaronstannard.com/the-profound-weakness-of-the-net-oss-ecosystem/
This has already been discussed in the past [1], and most people agreed that the reasons are bullshit because, yes, Mono [2] is alive and kicking.
[1] http://www.aaronstannard.com/post/2010/07/03/NET-Culture-Shock-Why-NET-Adoption-Lags-Among-Startups.aspx
[2] Not Xamarin.
There have been a few blog posts recently on this topic:
http://www.aaronstannard.com/post/2010/07/03/NET-Culture-Shock-Why-NET-Adoption-Lags-Among-Startups.aspx
http://tinpanvalley.tumblr.com/post/796605832/why-startups-dont-use-net