4 ms·
The naming truly sucks. You search for .NET and you find .NET framework, ASP.NET, .NET Core, .NET Framework, what even is .NET Xamarin MAUI? You look for a sol
by knallfrosch 3y ago
The naming truly sucks. You search for .NET and you find .NET framework, ASP.NET, .NET Core, .NET Framework, what even is .NET Xamarin MAUI?
You look for a solution and find an [AttributeDecorator] that no longer works or is considered bad practise, or is it the new silver bullet - who knows? You better return IHttpActionResult, or do you set the context.Response? Hmm.
It's much easier with younger Frameworks like Svelte, NestJS, Flutter or younger languages like TypeScript, GraphQL. You won't be told stuff that's been dead for 20 years.
- nfadili 3y agoThe naming situation has been the biggest barrier to adoption for me. I’d love a ‘definitive’ guide or set of docs for how to approach the ecosystem in 2023 if anyone has recommendations :)
- nfadili 3y agoWell here is a list of all of the words and their definitions, but the complexity still remains https://learn.microsoft.com/en-us/dotnet/standard/glossary https://learn.microsoft.com/en-us/dotnet/standard/glossary