,
18 tweets,
3 min read
Read on Twitter
Time for a panel discussion on the future of .NET, featuring @DamianEdwards, @davidfowl, @julielerman, @OdeToCode and @bryanjhogan 
Microsoft can't deliver everything by themselves, open source libraries will be a bigger part of the future
New JSON parser doesn't allocate at all. All async and no blocking
Lots of work going into bringing .NET Core Linux performance in line with Windows
EF Core is becoming more expressive. EF Core 2.2 is production ready
EF Core query pipeline is being rewritten to better separate client/server execution
Postgres EF provider has been improved, and improvements have even carried over into the core of ADO.NET
Microsoft SQL Client will be an out of band package instead of part of the framework
Pace of change has increased and it is important to keep up, otherwise costs will be higher later on. More breaking changes between major releases
Reluctance to move to EF Core is fading
.sln files are terrible
Retargetting from .NET Core 3.0 to .NET 5 should be fairly trivial
CoreFX APIs are now being deprecated, which never used to happen
Nuget packages can now be deprecated
The gap between Core and Framework won't get smaller (after v3.0) - start porting now
Balance between powerful language features (e.g. explicit memory management) and security
C# 9 may bring record types
More AOT options and tooling coming in .NET 5
