My favorite example of how far this convenience goes is demonstrated by items like the following from System.Numerics: public static System.Numerics.Matrix4x

My favorite example of how far this convenience goes is demonstrated by items like the following from System.Numerics: public static System.Numerics.Matrix4x4 CreatePerspectiveFieldOfView ( float fieldOfView, float aspectRatio, float nearPlaneDistance, float farPlaneDistance); https://learn.microsoft.com/en-us/dotnet/api/system.numerics.matrix4x4.createperspectivefieldofview?view=net-7.0 https://learn.microsoft.com/en-us/dotnet/api/system.numerics... I don't know of many other ecosystems that offer methods that allow for construction of FPS-friendly projection matrices in one first-party function call. If you peruse the docs you may find related methods that a game developer would find quite useful. You may also find that everything that can be SIMD-accelerated already has been. So, it's not just that .NET is convenient. Many of these conveniences are also approximately the fastest & safest way to do things since so much attention has been placed behind them. All of Microsoft's customers is a hell of a QA team. There is absolutely a herd mentality to this, and it works. Microsoft.* and System.* covers 99.99% of use cases if you simply allow them to. For me, this is the central competitive advantage that .NET has over most others. I do a lot of work with banks, and they audit the hell out of 3rd party. Every non-Microsoft nuget I pull down will need to be explained to our customers.