Re:Mono's New .NET Interpreter
by oaiey on Monday November 13, 2017 @01:28PM
(#15688711)
Right now it is kind of a cleanup phase ending with massive code reuse. But ultimately, I believe we continue to see both .NET Core and Mono flourish. Why? Because .NET Core and Mono have very different targets. Mono has nearly a decade of being factored into any kind of platforms while .NET Core and the CoreCLR will stay a workhouse for dedicated use cases. Same for the .NET Framework which has a full dedication to Windows with it's huge legacy and compatability burden.
[ Parent
| on HN ]
Re:Mono's New .NET Interpreter
by fauigerzigerk on Monday November 13, 2017 @02:10PM
(#15689189)
>Mono has nearly a decade of being factored into any kind of platforms while .NET Core and the CoreCLR will stay a workhouse for dedicated use cases.
I thought the "dedicated use case" of .NET Core was to be THE cross-platform .NET implementation.
Yeah. Cross platform server side.
With factored I meant more: native compiled, three shaked, WebAssembly compiled, iOS allowed, Arm, PowerPC, ....
Re:Mono's New .NET Interpreter
by fauigerzigerk on Monday November 13, 2017 @02:32PM
(#15689409)
That's the status quo for historical reasons, but I don't think many see this as a desirable state of affairs.
Agree. But reverting this is really hard. Because it is crucial to .NET to play both fields right now for the next ten years :). Reworking Xamarin is not an option in a time when the race against Cordova, React Native, Node, Swift, Go and Python is fully ongoing. They are pragmatic here, how they should be.
Re:Mono's New .NET Interpreter
by tonyedgecombe on Monday November 13, 2017 @03:49PM
(#15690099)
.NET Core is the gateway to Azure, I doubt we would see it on anything other than platforms developers might use.
The source code for .NET Core as on GitHub now powers .NET Core and UWP. It is a toolbox. We might not see .NET Core with a UI stack directly, but other factoring might happen. E.g. Samsung is using it for their Tizen platform in an own CoreCLR based factoring, including an UI Adapter between Tizen and the Xamarin.Forms abstraction. That is pretty much toolbox thinking. Now they can offer a .NET Standard 2.0 / Xamarin.Forms based programming environment with "little" effort.
To be honest, I would refrain to use Tizen as positive example of anything.
Samsung already rebooted the SDK so many times, and the platform lack of security is well known, I doubt it will ever get serious beyond a few watches and TV sets from Samsung.