News for hackers. Stuff that matters.

A comment on Mono's New .NET Interpreter. Parent comment

Re:Mono's New .NET Interpreter by oaiey on Monday November 13, 2017 @01:35PM (#15688773)
> How do you pick up one over the other?

I believe you do not have a choice. iOS, Android, macOS, Linux Desktop goes to Mono. No choice there. Application Servers go to .NET Core. No choice there considering performance and Cloud deployability. Windows Legacy goes to the .NET Framework. No choice there. Modern Windows App goes to UWP (another .NET Core).

I do not see a choice except when you want to run a service on Mono. Which everyone will tell you not to do.

[ Parent | on HN ]
Re:Mono's New .NET Interpreter by cosarara97 on Monday November 13, 2017 @01:51PM (#15688962)
> Which everyone will tell you not to do.

Why?

[ Parent | on HN ]
Re:Mono's New .NET Interpreter by oaiey on Monday November 13, 2017 @02:10PM (#15689178)
The performance is dramatically different (see TechEmpower benchmark) and the overall stability seems also a topic (the CoreCLR is pretty battle tested). Mono from it's first origin as GNOME technology till its current peak now in Xamarin somehow always played in the UI field (which has consequences on e.g. garbage collection or jitting).
[ Parent | on HN ]