but i'm even more glad modern .NET is already cross platform, without needing mono
but i'm even more glad modern .NET is already cross platform, without needing mono
Pi mean, .NET mobile and WASM uses mono
Pbut they've had the weirdness of having to maintain two separate codebases
Thaving wine take over seems very fitting
Tstill!?
Pyeah
Tyikes
Tcompatibility for legacy programs (and thus also games) is what wine is for, and also mono
Tso it's a good match
Ti hope good things come from this
Pbut yeah mono/mono has been a .NET Framework implementation (e.g. using the mscorlib from netfx) whereas dotnet/runtime/src/mono has been brought to be compatible with the .NET 5+ BCL for mobile purposes (i.e. One .NET)
Pgiven that, it makes so much sense for Wine to take over
Pgiven that they need ports of Windows components under their umbrella
Tmhm
GI do like that MS isnt being like Apple is with their OS
GSeems like they embrace WINE
Pwdym
Ti'm looking forward to the day when wine and mono aren't necessary anymore
but realistically that day will never come.. at least, not in my lifetime xD
so in the meantime, i will be appreciating the fact that they exist thoroughly
but realistically that day will never come.. at least, not in my lifetime xD
so in the meantime, i will be appreciating the fact that they exist thoroughly
Tmono wasn't a microsoft thing, though
it was a .NET Foundation thing
it was a .NET Foundation thing
Twhich maybe used to be a microsoft thing, but is now a standalone entity
Ahopefully they continue to upkeep mono though, i plan to use it heavily in my game. (yes, my C# game. seriously)
Tif i understand it all correctly
Twhat why 
Anice to see it moving to wine
Pmono was a community project that has passed hands. was Ximian, then Novell, then Xamarin, then Microsoft, then .NET Foundation with MS employed devs
Aneed runtime code execution, and that doesn't work with nativeaot. so i either write my own language, or use mono + ironpython to get python support with sandboxing
Toh dear
Ti see...
PSwift has been moved out of Apple into the Swift Foundation though, but there's not really an apt comparison given that there's no real equivalent project at Apple
Tsheesh
Kgod i still remember when mono was a small community project that people didnt really actively support
Kbut then again back in those days we still thought remoting was cool so like
GRemoting? like teamviewer?
Kno
Kremoting as in a system that automatically let you share object instances between processes
Guhhhh
Gyeah that sounds like hell
Gdefinitely cool & neat but sounds hellish to actually use
Kalso between appdomains
G:aPES_WideEyes:
Kwhich i dont have the energy to explain lol
Kit worked by automatically generating proxies and doing marshalling and i think the wire protocol was SOAP?
Kif youve ever seen MarshalByRefObject in dotnet that was the base class that signalled a thing should get remoted
Kremoting was superseded by WCF in dotnet framework 3.0 in 2006
Knot dotnet core 3.0 mind
Kframework 3.0
Goh i know
Kthat was also when WPF was introduced
Gi miss netcore3 :sadAngry:
Kjava RMI is the same thing as dotnet remoting if you know that
