Its really great, but some of the APIs could have been re-designed slightly when they "rebooted" the framework... e.g. getting rid of factory patterns when strictly not needed and such for added consistency.
Re:The .NET Core 2 Wave
by socrates666 on Monday January 23, 2017 @10:59AM
(#13463051)
Can I see an example? I get shifty when I see people saying things like 'factory pattern not strictly needed'. For example, there are moments where an API may need you to construct an object with a certain set of 'default properties'. I believe that rather than making developers generate 'boilerplate' there should just be some kind of 'boilerplate' factory.
So, these boilerplate factories are not strictly necessary but they make the API user's code simpler, more comprehensible, isolate responsibilities, etc.
Re:The .NET Core 2 Wave
by oceanswave on Monday January 23, 2017 @07:56PM
(#13467897)
Read the .net framework standard library annotated reference for some commentary by the original framework devs to understand what they would have changed.
It pretty much resembles the way .NET Framework also changed drastically from 1.0 to 2.0 which finally became the productive and trusted framework of today.
It's also really nice to be able to see all of this happening out in the open with the actual developers and leaders at Microsoft. They don't always make the right/best decision but at least they explain what they did and they're definitely taking feedback. It's very refreshing from the old .NET days where everything was opaque until the new release notes came out.