[TowerTall]

I don't think they are EEE-ing C#. I think what is going on is that there are middle management in the Visual Studio Full team that are very protective about the product they have help made and these manager are the ones that have a hard time adjusting to open source. Their salary is probably based on that VS has to make a profit or they simply don't understand open source of the benefits you (can) get. I dont think MS upper management has a formal EEE strategy. I simple it is some stupid middle management that f. up things

I dont know if c# has a future outside of games and big corps. I face palm everytime I see Microsoft launch something open source and cross platform and leave linux out of it and instead say that "the community must create something amazing for linux". If Microsoft starts to build the first version of shiny new thing for linux and launch it at the same time as the launch it for windows, mac, android, then i cam move outside those niches because doing that will create good will

[Dracophoenix]

For the moment, would you personally recommend building a web-server C#/.NET stack or would it be better to look elsewhere?

[TowerTall]

Absolutely I would. Everyone has their opinion about Microsofts products, but the platform and frameworks that underpin them are rock solid, long-time battle-tested in production, and easy to work with as a developer.

A .net stack comes with the comforting knowledge that this technology will never be made obsolete. It will undergo active development and will have support for many years to come. One day, long into the future, it will be super seeded by something else. When that happens, you know there will be a migration path because Microsoft has based their own business on it, and they need it for themselves, and all of their customers need it. .net does not go away tomorrow because something shinier showed up. That's nice to know.

You will find that you will have a very stable and mature stack that is well integrated with Azure making deployment and testing easy.

Was I to build a microservice application, I would not choose Kubernetes. I would choose the Microsoft Service Fabric Actor model over anything else that is out there.

Service Fabric is Microsoft Secret Sause. It is the technology that underpins the Azure Platform itself. Service Fabric has a beautiful actor model that makes the development of cloud-based applications as simple as writing a single threaded console application.

Service Fabric and Kubernetes: community comparison [1]

The Actor Model [2]

[1] https://docs.microsoft.com/en-us/archive/blogs/azuredev/serv...

[2] https://www.youtube.com/watch?v=7erJ1DV_Tlo

[Dracophoenix]

Service Fabric sounds like something too take into consideration. And It's certainly reassuring that .NET has staying power. But a major concern I have is whether .NET will run as well on an AWS Linux instance as it would on Azure.

So far what's caught my interest is Blazor as a Node.Js replacement. If you have had any experience, what's working with Blazor been like? How do you think it compares to other server-side frameworks like Node, Django, Pyramid, or Spring in terms of performance, feature-set, and maturity?

[TowerTall]

I don't know tbh. I work with big corps and it is mostly aspnet + angular I come across.