Mono's New .NET Interpreter

Re:Mono's New .NET Interpreter by oaiey on Monday November 13, 2017 @02:16PM (#15689247)

No the talk is from the .NET Rocks guys.

UWP/UAP is a new UI stack from the Windows team BOUND to a CoreCLR. That is different with the existing .NET UI technology stacks.

Additional, the CoreCLR and its more modern Assembly packaging (System.Runtime vs mscorlib) made the code difficult to share (recompile or PCL). This is solved now by the .NET Standard.

[ Parent | on HN ]

Re:Mono's New .NET Interpreter by pjmlp on Monday November 13, 2017 @02:24PM (#15689336)

> UWP/UAP is a new UI stack from the Windows team. That is different with the existing .NET technology stacks.

Which is what I meant with "mess created by Sinofsky regarding .NET, UWP and C++/CX.". I do have UWP experience since WP 8.

Thanks for the link about the talk.

[ Parent | on HN ]

Re:Mono's New .NET Interpreter by oaiey on Monday November 13, 2017 @02:40PM (#15689497)

Agree. History has not played nice with .NET but neither has with Java or Python.

[ Parent | on HN ]

Re:Mono's New .NET Interpreter by pjmlp on Monday November 13, 2017 @03:14PM (#15689792)

Two other favourite ecosystems of mine. :)

[ Parent | on HN ]

Re:Mono's New .NET Interpreter by oaiey on Monday November 13, 2017 @03:27PM (#15689902)

I think the only popular ecosystem with a positive trending history is JavaScript. But... Na I do not start there :)

[ Parent | on HN ]