News for hackers. Stuff that matters.
Re:Book of the Runtime – Internals of the .Net Runtime not i... by cm2187 on Thursday September 28, 2017 @07:46AM (#15356388)
Value tuples. If you want to use them you need to add a nuget package to the solution. I am not saying it's not doable, but it's a bad UX. Think of the experience of a newcomer to the language.
Re:Book of the Runtime – Internals of the .Net Runtime not i... by SimonPStevens on Thursday September 28, 2017 @09:16AM (#15356843)
I could be wrong, but I was under the impression that this was temporary.

The new tuple syntax in C#7 required the addition lf the ValueTuple class in the framework, but as framework and compiler versions are released independently it has to go into one first. This means people can upgrade their compiler to C#7, and install the ValueTuple nuget package and get the benefit of the new langauge feature without having to move their entire project to require the latest version of the .net framework. I believe the next version of the framework will include ValueTuple by default and the package will no longer be required.

Re:Book of the Runtime – Internals of the .Net Runtime not i... by cm2187 on Thursday September 28, 2017 @09:23AM (#15356900)
That's the reason why they did it. But that doesn't change my point on keeping it simple.
Re:Book of the Runtime – Internals of the .Net Runtime not i... by EpicEng on Friday September 29, 2017 @12:29PM (#15366716)
Ok, but the alternative is to simply wait longer for both the compiler and framework to be released together. There's no option C which gets you the feature just as quickly and still allows for parallel release of the two pieces need to implement it. So... Don't use the feature or be happy you have the ability to use it sooner.
Re:Book of the Runtime – Internals of the .Net Runtime not i... by SimonPStevens on Thursday September 28, 2017 @09:50AM (#15357088)
Yes, true.

Although at least in this case it will return to being simple at the next release.

But I do see your point, .net has certainly grown in complexity since the early days.

Re:Book of the Runtime – Internals of the .Net Runtime not i... by DougWebb on Thursday September 28, 2017 @10:14AM (#15357230)
I kind of like that; it's nostalgic for me. Most of my early career was spent writing Perl code, and in Perl it's possible, and common, to write optional add-on modules that give you new core language syntax. (Not everything is possible, but you can go a long way.)

For example, Perl 5 only has barebones support for OOP, and the community developed various approaches to fuller support. It was kind of like the way we've had multiple Javascript frameworks trying out various approaches to MVC. Eventually, Moose[1] was developed and became the most popular approach, and my understanding is that it greatly influenced the core support for OOP in Perl 6.

If you look at the docs for Moose, a lot of the syntax which looks like core language keywords is actually made of functions defined in the module.

This approach is great for letting the community of language users figure out what works and what's needed in the language, so that the language can evolve naturally instead of being designed by a detached committee. Again, it's much like the way Javascript is evolving, where the core language has been picking up features that were originally developed as add-on libraries.

[1] http://search.cpan.org/~ether/Moose-2.2006/lib/Moose.pm

Re:Book of the Runtime – Internals of the .Net Runtime not i... by zamalek on Thursday September 28, 2017 @12:33PM (#15358500)
It's how they release compiler versions at a different cadence to Visual Studio.