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

they're just unifying the core and full framework runtimes

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 *

https://mediastream.microsoft.com/events/2019/1905/Build/player/Track1.html?start=15515

microsoft and fucking up demos

name a more iconic duo

great banter from scott hanselman tho

>windows

That's wrong, that's the whole point

https://github.com/microsoft/terminal

they also opensourced conhost <:alithink:327930371796893698>

i wonder how many people have gotten fired/hired due they outsource the bughunt for hitclub

APOLOGIZE

https://www.youtube.com/watch?v=8gw0rXPMMPE

yoooooo

that looks pretty ok

anyone familiar with Haskell / wanna help me out

lel hasklel