undefined | Better HN

0 pointssjellis9y ago0 comments

In the last presentation that I saw, the line was that Mono would continue to exist as a full .NET implementation to support Xamarin mobile apps. The reason given was that .NET Core was scoped as a run-time for server applications, so no work had been done on making it run on mobile devices, whilst Mono has been used in production on those platforms for some time.

0 comments

oblio9y ago

That seems valid now. But developing two runtimes in parallel doesn't seem that great of an investment. Plus there are already dotnet core contributions regarding portability, for example from Samsung, it seems reasonable to think that 2-3-5 years from now dotnet core will power Mono as well.

sjellisOP9y ago

You could be right, the current situation is unsettled, so I'm personally reluctant to predict anything much. The argument for Mono seems to boil down to the MS teams not having enough capacity to get .NET Core production-ready for mobile whilst doing everything else.

I'm going to be learning ASP.NET Core, but not even think about possible production use until after the next release. We will probably continue to avoid .NET for mobile, and I would not consider Mono for any other use case.

oblio9y ago

Well, .NET Core is probably still 1-1.5 years away from being fully production "friendly". Common Open Source .NET libraries have to be ported, .NET Core itself needs to reach base class library parity at least as far as its scope is concerned (including things such as System.Drawing based on Skia# or similar), the tooling around it needs to mature.

Anything outside of ASP.NET Core or small command-line tools is probably premature in 2016.

j / k navigate · click thread line to collapse

0 pointssjellis9y ago0 comments

0 comments

oblio9y ago

sjellisOP9y ago

oblio9y ago

Anything outside of ASP.NET Core or small command-line tools is probably premature in 2016.

j / k navigate · click thread line to collapse