I read this as more a situation where an existing architecture got stuff shoehorned in for non-technology reasons. I don’t think there’s a problem with .NET in

I read this as more a situation where an existing architecture got stuff shoehorned in for non-technology reasons. I don’t think there’s a problem with .NET inherently. But swapping out components for new tech stacks for no user or tech reason is likely to introduce bugs and at best will negatively impact schedule. Although it would be interesting to hear any new company that chose .NET over other alternatives. I really likes how Spolsky explained why they used the MS stack [0] to build stackoverflow, among other things. [0] https://channel9.msdn.com/Blogs/Seth-Juarez/Joel-Spolsky-Talks-About-Building-Stack-Overflow-and-Values-Developers-Care-About https://channel9.msdn.com/Blogs/Seth-Juarez/Joel-Spolsky-Tal...