Message from @Goz3rr
Discord ID: 575014122522017792
unicode support is fucking long overdue
it also features shortcuts and extensions
at least microsoft is apparently even trying now
They're also renaming .NET again
After they release .NET Core 3.0
It's going to be .NET 5.0
Unifying core and framework
i take that back what i said just before now
🤦
Well it's sensible
And it's 5.0 because 4.0 already exists
They're going to make mono and coreclr drop in replacements
There will be just one .NET going forward, and you will be able to use it to target Windows, Linux, macOS, iOS, Android, tvOS, watchOS and WebAssembly and more.
ahh yes the "one thing to replace versions"
just like windows 10 has no more versions
1707, 1806 what else the different version numbers are what change the thing completly <:thonk:288060975775612929>
microsoft_so_good.jpg
it doesn't replace versions
it's .NET 5.0
and after it comes 6.0
and mono
did they say anything about backporting?
will I be able to run netfx 4.x on Linux?
no probably not
the way i'm reading it netfx will be completely replaced by coreclr
and coreclr will only be >net5?
coreclr will probably be backwards compatible with current .net standard
but not with netfx4
sad
also
Java interoperability will be available on all platforms
Objective-C and Swift interoperability will be supported on multiple operating systems.
<:kongoudisgust:570212220127019025>
CoreFX will be extended to support static compilation of .NET (ahead-of-time – AOT), smaller footprints and support for more operating systems
The default experience for most .NET 5 workloads will be using the JIT-based CoreCLR runtime. The two notable exceptions are iOS and client-side Blazor (web assembly) since both require ahead-of-time (AOT) native compilation.
I liked that we had one standard with many implementations
Net Standard had Mono, coreclr, netfx and unity
unity was mono too wasn't it
just a god awful old version
Now we have a standard with one implementation
A fork *