Slashdot Mirror
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."
It amazes me how people write stuff in Java without having a decent "Date" data type. Why should I have to use a third party library to get decent date support?
Java 8 introduced a new date time API. Admittedly I haven't used it as all of my code uses the old API. As far as the old API, one would use a Calendar when they are working with social dates and times and use a Date when working with an exact point in time. It isn't difficult.
Some identity providers (the "Log in with Twitter" bullshit) stupidly allowed people to authenticate with accounts that had unverified emails.
1: Create Twitter account with victim's email address.
2: Use "Log in with Twitter" bullshit on site.
3: Be granted access despite the email address associated with the Twitter account never being verified.
Some sites stupidly used the associated email address of the "Log in with Twitter" bullshit to match against existing users.
4: On such a site, you are granted access as the user with the email address you used in step 1.
There are three approaches to fixing this:
3: Twitter, Facebook, etc. should not provide identity services for accounts with unverified emails.
2: Sites should not trust (or even look at) the email address provided by an identity provider.
1: Site should simply NOT use this "Log in with Twitter" bullshit.
Never say never. But how about they stop extorting royalties from software patents first? That's pure evil by many programmers' standards. I'd also like to be clear that they are no longer in the business of inventing "standards" that are intended to make their own products incompatible with anything else. I see that their office software still doesn't use the Open Document format by default.
"It either works or it doesn't" - or it works for all but one or two hours of the year, around a time zone transition. Or it works so long as you're in a time zone which doesn't skip 00:00 when it transitions forward by an hour. Or it works so long as you're not in time zone which skipped a whole day once. How sure are you that all your code works in all of those conditions? How *clear* is your code in terms of which values are meant to be local, which are meant to be in UTC, and which are meant to be local in some other time zone?
You say that date manipulation in .NET is really not hard - but I've seen an *awful* lot of subtly-broken code using DateTime, and even correct code isn't always *obviously* correct, mainly because `DateTime` doesn't represent one single concept.
I looked at the .NET DateTime functionality *very* hard before deciding to write Noda TIme - and now, 5 years later, I'm still convinced that it was the right thing to do.