4 ms·
Definitely a frustration for those of us having done .Net for 20 years. Even the naming frustrates me. Every time they seem to create a new "one name to rule th
by lbriner 6y ago
Definitely a frustration for those of us having done .Net for 20 years. Even the naming frustrates me. Every time they seem to create a new "one name to rule them all", it only lasts a short while until a new one comes along net framework, .net core, .net standard .net 5 and apparently now .net 6.
As the OP said, the overarching problem is probably trying to be all things to all people and pretending that all of those things are .Net. It also produces a sadly common attitude now of "we won't fix that in dotnet core 3, upgrade to .net 5" as-if that is even a possibility for many existing apps.
One idea that comes from way back in the day was having an IDE that you could set to beginner, intermediate and advanced so that when you start out, you only see a subset of things. You can then get more confident in the basics before seeing more options and windows.
Another idea I liked was removing older features so that you don't keep getting bigger and bigger.
- andi999 6y agoYes. Naming is the worst. Oh, I have dotnet how do I make a webpage. Nah, you need also asp dot net. Or asp core .net, but this wont run on .net anymore but only on core .net..... headache...
- young_unixer 6y agoMicrosoft seem to have trouble naming things. Xbox One X, Xbox One S, Xbox series X, Xbox series S. And also: Is Outlook the same as Office365? Is Outlook the new Live? Did Hotmail turn into Live? Am I the only confused by all of this?