News for hackers. Stuff that matters.
Re:Porting the Unity Engine to .NET CoreCLR by kevingadd on Wednesday April 11, 2018 @01:58AM (#16808419)
I don't think they had any better options available to them at the time. Embedding and integration for an engine like Unity is just a tremendous challenge no matter what stack you use. I've done this sort of integration w/ various languages (python, lua, vbscript, c#, actionscript, javascript, etc) and C# is one of the most reasonable choices, if only because it was designed with native interop scenarios in mind. There are pointers, there are structs, etc.

Also keep in mind Unity did offer multiple scripting solutions - they had Boo for a while (eventually dropped), and there's UnityScript, though I'm not super familiar with how it works... C# is the one that won.

Re:Porting the Unity Engine to .NET CoreCLR by coldacid on Wednesday April 11, 2018 @04:01PM (#16814927)
Wasn't UnityScript just Unity-flavoured JS, like ActionScript was for Flash?