osu-framework VS dotnet

Related to your vision, you should definitely take a look at osu!framework. It's an open-source C# game engine, focused on 2D rendering and UIs. You can see the biggest example of it being used is, of course, osu! itself (osu!lazer, next iteration of osu!). It is so good that it has become my standard in terms of visual design and UI features.

An API I particularly like for this is how osu!framework does it.

Almost unrelated, but for game development (in C#), you might wanna look into the osu!framework, if at least just out of curiosity. It is a free and open-source game engine developed by peppy, the developer of osu!. You would also be able to develop on Linux (where programming tools really shine if you ask me) using VSCode and have neat things like visual tests and other stuff I haven't looked into.

it seems that despite using SDL, if you have "raw input" checked, it still uses the osuTK mouse input handler (https://github.com/ppy/osu-framework/blob/b97c26a684dc8ded5a349d24f8664a4f4b8c42a4/osu.Framework/Platform/DesktopGameHost.cs#L133, that's good)

My Favourite Graphics Engine at the moment is defnitly osu.Framework, you can find it here: https://github.com/ppy/osu-framework It can compile to .NET 5 and .NET 5 is cross platform now and the osu-framework makes smooth looking UIs with fancy transitions really really easy, it has some Audio Stuff in there aswell if you are looking to do something like that

Microsoft .NET Blog: https://devblogs.microsoft.com/dotnet/

Just find some good sites, that keep up with the news/changelogs ( one that I like for c# / dotnet stuff is is: https://devblogs.microsoft.com/dotnet/) as well as the whole c# roadmap on github and where they propose features, and design meetings (https://github.com/dotnet/csharplang/tree/main/meetings). It provides a lot of insight on what they plan on doing with the language). That's usually where I go to keep up with c# stuff.

Microsoft's .NET blog is pretty good for seeing what they're up to.

The .NET Blog has great articles about new and upcoming changes.

how exactly does dotnet 5 acheive this? it makes sense for dotnet 6 since we have different TFM's like net6.0-android, net6.0-ios, net6.0-macos etc. however, if you look for dotnet 5 you only have net5.0 and net5.0-windows TFMs as per given link, https://learn.microsoft.com/en-us/dotnet/standard/frameworks also somebody asked the question how to run .net 5 app on android and the answer given was to preferably still use xamarin/mono, https://github.com/microsoft/dotnet/issues/1253 Also what exactly did change in this regard, does it use same core clr, does it use the same base class library as one used in dotnet core?

Bookmark https://devblogs.microsoft.com/dotnet/ and read occasionally. https://docs.microsoft.com/en-us/dotnet/csharp/whats-new/csh... is good for a quick overview of language features depending on what version you're at.

Most .NET devs only need to be peripherally aware of these changes, as most businesses using .NET will move slower than Core's new pacing. It's even less important for lower seniority devs as you typically need project changes to utilize new features, which is a call a senior would make, which involves approval/testing/deployment, so a slow process which gives you time to read up on the new features as they're needed.

You're better at your "craft" the more tools you know about and how to apply them, but if your day job prevents you from following the new stuff, I wouldn't worry too much about it.

>I feel .NET Core after a good start is falling into the typical Microsoft trap of constantly cranking out new stuff to do the same thing and leaving it to developers to keep up.

Yeah, the pacing has increasing dramatically from .NET Framework days, but that's probably a good thing. I would just stick to learning about what you do in your day job. .NET has a huge ecosystem compared to other languages, so it's going to be very hard to keep up with everything MAUI is doing if you're doing regular ASP.NET core APIs.

Release Notes

.NET home repo - links to hundreds of .NET projects, from Microsoft and the community.