Sorry, I did not mean to suggest that .NET Core was more portable than Mono, or even that it is "better" than Mono. They are actually quite different. Mono is an open source implementation of the traditional .NET framework (e.g., .NET 4), while .NET Core is a new framework that was written from scratch. Pick you tools for your purposes.
Based on what little I have read, it looks like Mono will use .NET Core wherever it can. The Mono community has already started incorporating parts of .NET Core into Mono. Xamarin, a mobile app development platform based on Mono, is owned by Microsoft. So it is likely that Xamarin will also start incorporating .NET Core where possible. I don't think .NET Core will completely replace Mono because Mono has functionality that .NET Core does not. However, growing success by .NET Core might draw developers away from Mono, especially if Microsoft comes out with a something to "supplement" .NET Core with functionality found in Mono. So, for example, Mono => .NET Core + MS supplement, or perhaps Mono => .NET Core Extended. That might leave a Mono port to PASE with a small Mono-for-i community of developers and no commercial support.
In terms of waiting for .NET Core to come to the IBM i...nope, we won't be waiting. But we're not waiting for Mono to work out all the kinks and prove its performance and reliability either. There are a lot of technologies on the IBM i that do what we need to do. We're evaluating technologies now. Mono might get put on our list to evaluate, but in its current state it might not make the short cut.
Thanks,
Kelly Cookson
IT Project Leader
Dot Foods, Inc.
217-773-4486 ext. 12676
www.dotfoods.com<
http://www.dotfoods.com>
From: OpenSource <opensource-bounces@xxxxxxxxxxxx> On Behalf Of John Yeung
Sent: Thursday, November 1, 2018 11:15 AM
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Subject: Re: [IBMiOSS] [EXTERNAL] Mono Port To IBM i Now Available
On Thu, Nov 1, 2018 at 8:57 AM Kelly Cookson <KCookson@xxxxxxxxxxxx<mailto:KCookson@xxxxxxxxxxxx>> wrote:
I think some concerns from our shop would be: [...] (4) questions about the future of Mono given the open source, multi-platform .NET Core alternative (though Mono and Core may be slowly converging, since Core is open for use by the Mono community and Microsoft owns the Mono-based Xamarin mobile app platform).
Despite its billing, it's debatable whether .NET Core is "more
multiplatform" than Mono. So far, it's still far easier to port Mono
itself than .NET Core. As for long-term strategy, it's hard to say.
Mono will still be around and important for quite some time (somewhere
between "several" and "many" years, I'd guess).
Most importantly in my mind, Mono is already largely here. (Obviously
the database issue has to be solved, but that strikes me as a very
tractable problem.) If you want to wait for .NET Core to arrive on the
i, you could be waiting a very long time.
John
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx<mailto:OpenSource@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/opensource<
https://lists.midrange.com/mailman/listinfo/opensource>
or email: OpenSource-request@xxxxxxxxxxxx<mailto:OpenSource-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/opensource<
https://archive.midrange.com/opensource>.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com<
https://amazon.midrange.com>
midrange.com
