Hey Lionel, so the Mono port that you refer to was based on (I believe) dotNet 3 - MS with their re-architecting of the dot net code base (after the acquisition of Ximian (sp?)) merged the external mono code base with their previously proprietary code base and released pretty much all of the core of .Net as version 6 last year, and version 7 is in RC now. All of the changes our team has made (and yes, Janani is my team lead for the port) are currently upstream and in .Net 7 RC. We are still tracking down a few defects found while running the native build or some of the tests but we have a running demo that a couple of customers are trying as a technology preview. It is pretty much just build from upstream, although the process is awkward enough that most people probably don't want to do that, even though they could.
Since MS integrated two code bases, they have two runtimes now - the original MS formerly-propriety coreclr and the evolution of the previously open source Mono. We have NOT ported coreclr at this point, only Mono, but that should get us full functionality, possibly missing some performance benefits in the runtime that MS focuses on the most.
I hope this helps, but definitely shout out if you have further questions!
------------------------------
Gerrit
------------------------------
Original Message:
Sent: Thu October 06, 2022 04:08 PM
From: Lionel Clavien
Subject: .NET on Power
Hi Gerrit,
Since Mono on ppc64le has been available for some years (tested it successfully on an AC922 2-3 years ago), what is the difference with the work your team is currently carrying on? Is Janani (https://github.com/janani66) part of that team?
Thanks,
------------------------------
Lionel Clavien, PhD
IBM Champion for Power
CTO & Co-founder
InnoBoost SA
Lausanne, Switzerland
Original Message:
Sent: Thu October 06, 2022 03:15 PM
From: Gerrit Huizenga
Subject: .NET on Power
Just for clarity, the preview of .NET work is for .NET on Linux on Power (not AIX or IBM i, at least not from our team) and there is the current limitation that we are doing the mono runtime only at this point, not the coreclr runtime which is where MS has been putting a lot of their performance investment. We are hoping to get to coreclr "next" but we don't have a time frame or committed date on that as yet. However, we are seeing a LOT of requests from customers - mostly mid-size/regional banks for the .NET capability. As with many things, we chose the mono runtime first because it is quicker/easier to port and should provide all of the functionality although it may not have the performance that coreclr will show on Intel. Also, we are planning on delivering this as a container initially, especially for our "tech preview" uses, which makes it ideal for use within OpenShift, as well as hopefully integrating with Red Hat's Dev Spaces (IDE) environment in the future.
Just my $0.22. ;)
------------------------------
Gerrit
Original Message:
Sent: Thu October 06, 2022 10:41 AM
From: Paulo Ricardo Stradioti
Subject: .NET on Power
I think that Mono was very limited compared to the power of .NET Core (not just .NET).
Also, considering the major performance improvements that Microsoft has introduced in the latest versions (6 and 7 mainly), I think the demand for .NET on OpenShift will most likely increase in the next couple years.
------------------------------
Paulo Ricardo Stradioti
Original Message:
Sent: Thu October 06, 2022 09:16 AM
From: Peter Czanik
Subject: .NET on Power
I have some mixed feelings about it. Probably both are true to a degree. I mean .NET (mono) support was available on Linux for quite some time, but it never really took off even on x86. Yes, there are some applications, developers migrating from Windows to Linux were happy to see a familiar looking language. But that is all.
There is a mass exodus from Windows web servers to Linux in the past years. Many times the web applications are not really migrated but developed from scratch on Linux again in other programming languages. However, I heard about a bank, where Windows web applications were moved with minimal changes to an OpenShift + mono environment. It saved quite a lot of time and effort, compared to developing everything again from scratch. So, yes, .NET in a non-Windows environment is a thing, and in a really well paying environment: banks. But it seems to be a minority, and Power would be a minority within this minority.
------------------------------
Peter Czanik
Original Message:
Sent: Fri September 23, 2022 03:53 AM
From: Torbjörn Appehl
Subject: .NET on Power
Hi,
As you can see here PowerPC and AIX support · Issue #10055 · dotnet/runtime| GitHub | remove preview |
 | | PowerPC and AIX support · Issue #10055 · dotnet/runtime | | You can't perform that action at this time. You signed in with another tab or window. You signed out in another tab or window. Reload to refresh your session. Reload to refresh your session. | | View this on GitHub > |
|
|
.net is on the way to Power via Redhat Openshift.
My questions is very open. Do you think this is hot as lava, or is .NET already a dying language? (I get both responses when I talk to ISV's about this..)
------------------------------
Torbjörn Appehl
------------------------------
------------------------------
Torbjörn Appehl
------------------------------