4 ms·

What about Mono? I have no idea how practical this is for real code bases, but I've used it successfully on several smaller projects.

gabriel 13y ago
Mono is quite practical. However, C# is one thing, and the .NET Memory Model is quite another. The memory model is, IMHO, where Microsoft is pushing the limits of the existing C# language.
- dewiz 13y ago
  could someone point to some article that expand on this topic ? thanks
- tanzam75 13y ago
  > The memory model is, IMHO, where Microsoft is pushing the limits of the existing C# language. What has Microsoft changed in the .NET memory model that makes you think they're pushing the limits? From what I can tell, the .NET memory model is one of the things that has changed the least. The languages have changed a lot faster than the memory model.
Moto7451 13y ago
I have Mono projects in production. Xamarin Studio is pretty nice these days. I don't have a lot of performance sensitive .Net code so I don't notice any real difference between Microsoft's and Xamarin's implementations. One problem I'm running into at the moment is I'm trying to port a vendor's reference SOAP Service over to Mono/Linux and their provided secret sauce DLL is blowing up when calling their objects' constructors. I'm yet to pin it on Linux or Mono. Here's hoping the vendor is Mono friendly and willing to debug it. If not we're going to have one oddball Windows server in a sea of Ubuntu EC2 instances.
- itsboring 13y ago
  Same here, a number of Mono apps in production, both on mobile and desktop. A lot of my recent work has to do with OpenGL-related stuff running on Linux using Mono/MonoDevelop. I have had neither performance-related issues nor stability issues. Ironically, we have some large-ish C# code-bases that run on everything but Windows.
- LordIllidan 13y ago
  Personally, I find Xamarin Studio to be quite buggy, often needing several quit+restart a day (I do iPhone apps), a colleague also does Android apps with Xamarin (on Windows) and experiences similar problems.

gabriel 13y ago

Mono is quite practical. However, C# is one thing, and the .NET Memory Model is quite another. The memory model is, IMHO, where Microsoft is pushing the limits of the existing C# language.

dewiz 13y ago
could someone point to some article that expand on this topic ? thanks
tanzam75 13y ago
> The memory model is, IMHO, where Microsoft is pushing the limits of the existing C# language. What has Microsoft changed in the .NET memory model that makes you think they're pushing the limits? From what I can tell, the .NET memory model is one of the things that has changed the least. The languages have changed a lot faster than the memory model.

Moto7451 13y ago

I have Mono projects in production. Xamarin Studio is pretty nice these days. I don't have a lot of performance sensitive .Net code so I don't notice any real difference between Microsoft's and Xamarin's implementations. One problem I'm running into at the moment is I'm trying to port a vendor's reference SOAP Service over to Mono/Linux and their provided secret sauce DLL is blowing up when calling their objects' constructors. I'm yet to pin it on Linux or Mono. Here's hoping the vendor is Mono friendly and willing to debug it. If not we're going to have one oddball Windows server in a sea of Ubuntu EC2 instances.

itsboring 13y ago
Same here, a number of Mono apps in production, both on mobile and desktop. A lot of my recent work has to do with OpenGL-related stuff running on Linux using Mono/MonoDevelop. I have had neither performance-related issues nor stability issues. Ironically, we have some large-ish C# code-bases that run on everything but Windows.
LordIllidan 13y ago
Personally, I find Xamarin Studio to be quite buggy, often needing several quit+restart a day (I do iPhone apps), a colleague also does Android apps with Xamarin (on Windows) and experiences similar problems.