3 ms·
It's very possible that MS did all of the right things here, and still did a terrible job of messaging it.
by cwyers 7y ago
It's very possible that MS did all of the right things here, and still did a terrible job of messaging it.
- merb 7y agoactually i think .net 5 will clear a lot of stuff up. basically there is no more naming confusion and once we are on asp.net 6 no version conflicts will ever be there. its the best step they could do. they also communicate clearly now that there will only be one dotnet implementation in the future, .net 5 and forward. in the past there was no clear message what will happen with mono, .net4x, etc...
- caspper69 7y agoIt's also possible people have reading comprehension problems.
- cwyers 7y agoSure, but you can view things as "where do I assign blame" or "what are my fixed inputs." If you look for something to blame, maybe it's that people lack reading comprehension. If it's enough people getting confused, and it matters to you that people understand things -- even if things would be solved by them reading/understanding the right things, you need to change what you can change, because you can't change your fixed inputs (in this case, your audience).