3 ms·
Is Mono not dying due to .NET core? It seems to be popping up in a few new places but I would have thought new projects would be avoiding it. The last thing I
by jasonkostempski 9y ago
Is Mono not dying due to .NET core? It seems to be popping up in a few new places but I would have thought new projects would be avoiding it.
The last thing I want is any dependency on MS tooling as they've shown everything they release will include telemetry. I'm just getting started with game dev and I really like Godot, but if the future is going to require MS anything, I'm going to jump ship.
- Rapzid 9y agoI have bad news for you; Mono 5.0 launched with Roslyn which I believe is what brings C#7 support. Roslyn is of course a MS project. Ditto for MSBUILD.
- jasonkostempski 9y agoSo will installing a version of Godot that supports C# get me something reporting back to MS out of the box?
- kevingadd 9y agoMono is still supported. .NET core and Mono solve different problems - for example (this surprised me), unlike Mono and the windows .NET Framework, .NET core can't just run random .NET executables you download off the internet. You have to build a core-targeted project from source. Mono also handles cross-platform scenarios like mobile & mac frontend apps right now that .NET core won't be a good fit for in the near future.
- cptskippy 9y agoMono, .NET Framework, .NET Core, Xamarin.<Platform>, etc are all just different implementations of .NET Standard. I believe .NET Framework is a superset of Core. They can all run code targeted at Standard but all have slightly different libraries on top of Standard. Mono was originally was intended to be a cross platform stand-in for .NET Framework which is why they can mostly run the same code. I believe Mono and Framework are slowly merging together.
- AdeptusAquinas 9y agoI don't think this is true. Framework for example can only reference standard libraries as of 4.6.2. Up until dotnet core 2.0, core was very much an incompatibile subset of framework - even with 2.0 it would be better characterised as a cross platform rewrite of the net framework.
- pjmlp 9y agoActually .NET Standard 2.0 requires .NET 4.6.1. .NET 4.6.2 was only for .NET Standard 1.0, but they realised basing on 4.6.1 would be a more sensible decision and fixed it in version 2.0.