4 ms·
As well as the underlying .NET Core framework, and .NET in general. We have great new memory types like Span<T> and Memory<T> and tiered compilation, along with
by manigandham 8y ago
As well as the underlying .NET Core framework, and .NET in general. We have great new memory types like Span<T> and Memory<T> and tiered compilation, along with thousands of other improvements that has made major improvements in performance.
- pjmlp 8y agoWhich aren't being fully backported to .NET Framework, whereas many libraries still don't run on Core.
- manigandham 8y agoSo? We're talking about .NET Core here. These new APIs are compatible with netstandard, so they can still be used with Framework but wont be as fast. What libraries are using these newer APIs but refusing to target Core?
- pjmlp 8y agoODP.NET for example. Managed ODP.NET for Core is a partial implementation of the ODP.NET for the full .NET Framework. Libraries using EF 6, because EF Core is still playing catchup with EF 6, and even .NET Core 3.0 won't support 100% of the EF 6 tooling. Libraries using WCF, which lack budget for anyone to rewrite them and the respective clients into other transport protocols. Plenty of other examples.