Monday, May 13, 2019 [Tweets] [Favorites]

.NET 5 = .NET Core vNext

Microsoft (Hacker News):

Today, we’re announcing that the next release after .NET Core 3.0 will be .NET 5. This will be the next big release in the .NET family.

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.

[…]

This new project and direction are a game-changer for .NET. With .NET 5, your code and project files will look and feel the same no matter which type of app you’re building. You’ll have access to the same runtime, API and language capabilities with each app. This includes new performance improvements that get committed to corefx, practically daily.

[…]

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

Frank A. Krueger:

What lessons can be learned from .NET Framework’s replacement by .NET Core/.NET 5? Platform lock-in is bad? Backwards compatibility can only be achieved for fixed time? Consolidation’s energy efficiency outweighs diversity? Names are arbitrary? Sic transit gloria mundi?

See also: .NET Dynamic Code Execution.

Previously:

1 Comment

$0.02: "Thus passes the glory of the world," qua "Nothing is permanent," afaict.

https://en.wikipedia.org/wiki/Sic_transit_gloria_mundi#Other_uses

Stay up-to-date by subscribing to the Comments RSS Feed for this post.

Leave a Comment