Discover and read the best of Twitter Threads about #dotnetstandard
Most recents (1)
This latest thing with #dotnetcore and #dotnetstandard is understandable, but also unavoidable, I think. Core lets the team move faster and break things because you don't have to upgrade it globally on a box; you can have 2.0 and 2.0.4 and 2.1 apps in isolation. 1/
You can't do that with full NetFX (or Mono?) so updates have to be much more cautious. Going from 4.7.2 to 4.8 will affect all apps running on that box. And with the Core 2.1 changes, a LOT of BCL APIs have changed. 2/
I suspect there will be a lot of internal discussions and meetings about getting, for example, the Span/Memory APIs into a shared .NET Standard, making sure the implementations and semantics are properly understood by everyone who needs to implement them. 3/
