How do you quantify engineers’ productivity? A Java or a Python developer (much easier to find than a .NET developer) will be a lot more productive in Java or Python. And it is not a universal fact that .NET developers are more productive than others. Python developers would argue the other way round.
Point is - if a team is more productive using python they should use python. If it’s c# then they should use c#. Licensing cost doesn’t figure into the decision. People who complain about exorbitant licensing cost leave me confused because I do t see those costs.
And, once you have started with Java/Python, why would you want to spend your money on licensing costs AND .NET developers who, from personal experience, often tend to be more expensive and harder to hire than Java/Python/Go developers?
Licensing costs don’t matter a lot if you already have a team that is proficient in .NET. It’s a Catch-22 situation. Why would want to spend money on building a team of .NET developers in the first place unless you have some hard evidence that using .NET is going to help your business significantly?
Stacks also have the varying number of "batteries" included, and on Linux, the Microsoft stack comes with very few "batteries".
Windows tax amounts to about 30% bump in AWS ec2 costs. Typical CRUD startup will have their costs dominated by payroll, not hosting. If I can get my engineers 3% more efficient at the cost of making my hosting 30% more expensive I will do this in a heartbeat.
What is the situation where you experience onerous Windows tax?