@davidfowl Not at all, that’s a common phenomenon. Java is no different. I see an opportunity of keeping api surface reduced to the “current way” of doing things in dotnet and make legacy an extension. I often see devs lured towards minimalistic lang and frameworks and it says something.
@davidfowl My point is the the stigma lives on at the form of legacy support. Which is only great if you actually need legacy support, which is not the case (or shouldn’t be) for any new project.
@davidfowl Open up VS, hit dot and you see it suggesting all these Begin/End legacy async model for socket and 54 different timer apis. Google it and it’s all stuff you shouldn’t use anymore. One can see how it might scary a newcomer unaware of .NET2.0 and all the evolution till today.
@azuresupport#azTechHelp Where are the old Application Insights tiles ? They were convenient to fast add charts to dashboards without writing log queries. Disappointing they are gone.