Message from @Goz3rr

Discord ID: 575014014950834196


2019-05-06 17:00:50 UTC  

nothing is stopping you from disabling that

2019-05-06 17:00:57 UTC  

i don't even know if that's the default either

2019-05-06 17:01:20 UTC  

tabs is welcome upgrade thp

2019-05-06 17:01:27 UTC  

unicode support is fucking long overdue

2019-05-06 17:02:52 UTC  

it also features shortcuts and extensions

2019-05-06 17:06:40 UTC  

at least microsoft is apparently even trying now

2019-05-06 17:10:42 UTC  

They're also renaming .NET again

2019-05-06 17:10:56 UTC  

After they release .NET Core 3.0

2019-05-06 17:11:04 UTC  

It's going to be .NET 5.0

2019-05-06 17:11:16 UTC  

Unifying core and framework

2019-05-06 17:11:18 UTC  

i take that back what i said just before now

2019-05-06 17:11:29 UTC  

🤦

2019-05-06 17:11:52 UTC  

Well it's sensible

2019-05-06 17:12:07 UTC  

And it's 5.0 because 4.0 already exists

2019-05-06 17:12:37 UTC  

They're going to make mono and coreclr drop in replacements

2019-05-06 17:15:22 UTC  

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.

2019-05-06 17:32:02 UTC  

ahh yes the "one thing to replace versions"

2019-05-06 17:32:13 UTC  

just like windows 10 has no more versions

2019-05-06 17:32:41 UTC  

1707, 1806 what else the different version numbers are what change the thing completly <:thonk:288060975775612929>

2019-05-06 17:33:02 UTC  

microsoft_so_good.jpg

2019-05-06 17:40:24 UTC  

it doesn't replace versions

2019-05-06 17:40:28 UTC  

it's .NET 5.0

2019-05-06 17:40:33 UTC  

and after it comes 6.0

2019-05-06 17:40:50 UTC  

they're just unifying the core and full framework runtimes

2019-05-06 17:40:55 UTC  

and mono

2019-05-06 18:30:28 UTC  

did they say anything about backporting?

2019-05-06 18:30:45 UTC  

will I be able to run netfx 4.x on Linux?

2019-05-06 18:32:01 UTC  

no probably not

2019-05-06 18:32:16 UTC  

the way i'm reading it netfx will be completely replaced by coreclr

2019-05-06 18:32:34 UTC  

and coreclr will only be >net5?

2019-05-06 18:33:45 UTC  

coreclr will probably be backwards compatible with current .net standard

2019-05-06 18:33:54 UTC  

but not with netfx4

2019-05-06 18:33:56 UTC  

sad

2019-05-06 18:34:00 UTC  

also

2019-05-06 18:34:02 UTC  

Java interoperability will be available on all platforms

2019-05-06 18:34:07 UTC  

Objective-C and Swift interoperability will be supported on multiple operating systems.

2019-05-06 18:34:10 UTC  

<:kongoudisgust:570212220127019025>

2019-05-06 18:35:06 UTC  

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.

2019-05-06 18:35:50 UTC  

I liked that we had one standard with many implementations

2019-05-06 18:36:06 UTC  

Net Standard had Mono, coreclr, netfx and unity

2019-05-06 18:36:13 UTC  

unity was mono too wasn't it