Aaron Stannard
aaronstannard.com · Personal blog · on HN since 2010
Aaron Stannard, a .NET developer and Akka.NET co-founder, writes on the .NET open source ecosystem, startups, and developer skill.
What HN saysHN links it in debates over why .NET lags among startups and how Microsoft shapes the .NET open source ecosystem.
43HN people shared it
6linked it in comments
63stories submitted
1.4Kstory points
2 months agolast shared
2010people per year2026
Most-shared posts
- 1The Weakness of the .NET OSS Ecosystem3 people · 174 points · first shared 2015 · 207 comments on HN
- 2The Taxonomy of Terrible Programmers3 people · 167 points · first shared 2013 · 130 comments on HN
- 3Developers who can build things from scratch3 people · 135 points · first shared 2015 · 43 comments on HN
- 4.NET Culture Shock: Why .NET Adoption Lags Among Startups3 people · 27 points · first shared 2010 · 69 comments on HN
- 5.NET Core Is Boiling the Ocean2 people · 137 points · first shared 2016 · 40 comments on HN
- 6.NET Developers Begging for Ecosystem Destruction2 people · 54 points · first shared 2024 · 29 comments on HN
- 7.NET Open Source: What Happens When the Free Lunch Ends?2 people · 38 points · first shared 2021 · 22 comments on HN
- 8Why You’re Failing to Realize Your Potential as a Developer2 people · 37 points · first shared 2013 · 27 comments on HN
- 9The Coming .NET Renaissance2 people · 33 points · first shared 2017 · 4 comments on HN
- 10There Has Never Been a Better Time to Be a Junior Dev – It Won't Last Forever2 people · 5 points · first shared 2025 · 1 comments on HN
- 11NET Core Is Probably Fine2 people · 5 points · first shared 2017 · discussion on HN
- 12How to Build Sustainable Open Source Software Projects2 people · 5 points · first shared 2020 · 1 comments on HN
- 13Escaping the LLM Coding Rat Race2 people · 4 points · first shared 2026 · discussion on HN
- 14The Future of AI Belongs to Experienced Operators with Good Taste2 people · 3 points · first shared 2025 · 1 comments on HN
- 15The New Rules for Playing in Microsoft's Open Source Sandbox2 people · 3 points · first shared 2020 · discussion on HN
What HN people wrote when they linked it
Aaronontheweb · 2021-10-05
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/
platz · 2016-11-24
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-ecos…
r721 · 2015-07-03
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.
knocte · 2013-08-03
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…
[2] Not Xamarin.
hiester · 2010-07-29
There have been a few blog posts recently on this topic:
http://www.aaronstannard.com/post/2010/07/03/NET-Culture-Shock-Why-NET…
http://tinpanvalley.tumblr.com/post/796605832/why-startups-dont-use-ne…
yukichan · 2014-03-22
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-mongo…
[4] http://www.aaronstannard.com/post/2013/12/19/The-Taxonomy-of-Terrible-…