> C# is just a better fit than Java. I'm not sure I follow: having access to lower level functionality is good, of course, but I don't think that's quite the d

> C# is just a better fit than Java. I'm not sure I follow: having access to lower level functionality is good, of course, but I don't think that's quite the deciding factor for the majority of folks, who want to knock together a game. Number crunching will be relevant for a limited subset of game projects out there, otherwise Lua wouldn't have seen widespread usage, or maybe something like GDScript wouldn't have been created in the first place. In regards to Span<T>, wasn't it added relatively recently? That seems to be the case, from what I can tell: https://learn.microsoft.com/en-us/dotnet/api/system.span-1?view=net-7.0 https://learn.microsoft.com/en-us/dotnet/api/system.span-1?v... Applies to Product Versions .NET Core 2.1, Core 2.2, Core 3.0, Core 3.1, 5, 6, 7 .NET Standard 2.1 That seems to be confirmed by this: https://devblogs.microsoft.com/dotnet/announcing-net-standard-2-1/ https://devblogs.microsoft.com/dotnet/announcing-net-standar... Span<T>. In .NET Core 2.1 we’ve added Span<T> which is an array-like type that allows representing managed and unmanaged memory in a uniform way and supports slicing without copying. And yet, C# and .NET (or Mono) were already used by popular engines like Unity all the way back in 2005, so surely there's more at play here! Maybe what held Java back were social reasons, like concerns around licensing, or how easy it would be to integrate JDK or package it back in the day and so on.