News for hackers. Stuff that matters.
Re:Porting the Unity Engine to .NET CoreCLR by lostmsu on Tuesday April 10, 2018 @03:43PM (#16804545)
CoreCLR so far does not work on either Android or iOS AFAIK.
Re:Porting the Unity Engine to .NET CoreCLR by aras_p on Tuesday April 10, 2018 @03:51PM (#16804640)
Correct, right now it's only Windows/Mac/Linux. That leaves the whole mobile & console platforms without it, so it's not like our IL2CPP stuff is "not needed anymore".
Re:Porting the Unity Engine to .NET CoreCLR by sebazzz on Tuesday April 10, 2018 @04:11PM (#16804845)
I wonder then if CoreRT will be able to play a role then.
Re:Porting the Unity Engine to .NET CoreCLR by drawkbox on Tuesday April 10, 2018 @04:06PM (#16804793)
Hey Aras you guys are doing a good job.

So I guess CoreCLR will cause more work for Unity engine teams in the interim.

IL2CPP is great right now and gets past all AOT issues as the initial pain is over. Ralph Hauwert and those guys did a good job. It also gets compilation AOT down to C++ so it cannot be messed with by Apple. But I guess CoreCLR will be another standard/lib to manage and suddenly the standard xkcd on standards becomes relevant [1].

I can still dream of Unity Plan B from 2010 though with a fully C++ API that mimics the C# one.

[1] https://xkcd.com/927/