Microsoft Introduces .NET Core
New submitter I will be back writes: Microsoft's Immo Landwerth has provided more details on the open source .NET Core. Taking a page from the Mono cookbook, .NET Core was built to be modular with unified Base Class Library (BCL), so you can install only the necessary packages for Core and ship it with applications using NuGet. Thus, NuGet becomes a first-class citizen and the default tool to deliver .NET Core packages.
As a smaller and cross-platform subset of the .NET Framework, it will have its own update schedule, updating multiple times a year, while .NET will be updated once a year. At the release of .NET 4.6, Core will be a clear subset of the .NET Framework. With future iterations it will be ahead of the .NET Framework. "The .NET Core platform is a new .NET stack that is optimized for open source development and agile delivery on NuGet. We're working with the Mono community to make it great on Windows, Linux and Mac, and Microsoft will support it on all three platforms."
As a smaller and cross-platform subset of the .NET Framework, it will have its own update schedule, updating multiple times a year, while .NET will be updated once a year. At the release of .NET 4.6, Core will be a clear subset of the .NET Framework. With future iterations it will be ahead of the .NET Framework. "The .NET Core platform is a new .NET stack that is optimized for open source development and agile delivery on NuGet. We're working with the Mono community to make it great on Windows, Linux and Mac, and Microsoft will support it on all three platforms."
Why should I have to use a third party library to get decent date support?
Hey now, a Java Calendar object is roughly half a kilobyte (really), surely there must be some useful functionality in there somewhere! Right? Well, I can't parse a string into a date using Calendar, I can't add any sort of "duration" object to a Calendar, though I can do "add(Calendar.DAY_OF_MONTH, -5)", so there's that.
Java doesn't support List, doesn't have a in-built String.IsNullOrEmpty, doesn't have C#'s wonderful "??" operator for null-fixing, doesn't have proper properties (is that redundant?) but here I am stuck using it.
C# is about 8 years ahead of Java at this point.
Socialism: a lie told by totalitarians and believed by fools.