News for hackers. Stuff that matters.
Re:The Problem with F# Evangelism by com2kid on Wednesday August 16, 2017 @11:59AM (#15028519)
> Functional programming is also seeping in but again tons of boiler plate.

The bar has moved so much on this one. I remember when C#'s wonderful lambda syntax, along with all the extension methods that LINQ added, qualified it as having pretty good functional programming support. Now that other languages have gone out and copied sane lambdas, and "Map" is in libraries left and right, C# has to keep reaching for that higher and higher bar.

Re:The Problem with F# Evangelism by louthy on Wednesday August 16, 2017 @02:47PM (#15030046)
What does the higher bar look like to you? For me, the major missing features of C# are:

* Immutable record types

* ADTs with completeness pattern matching

* Higher-kinds

F# is also missing higher kinds, but can do the others. Did you have something else in mind?

Re:The Problem with F# Evangelism by pjmlp on Thursday August 17, 2017 @02:24AM (#15034214)
None of them makes me write prettier GUIs or better use of EF.
Re:The Problem with F# Evangelism by naasking on Thursday August 17, 2017 @04:51AM (#15034914)
Actually, higher kinds could make you write more composable and reusable GUIs. I don't see why "prettier" is the only metric of interest.

Immutable records also makes it easier to share data safely, thus making scaling across cores easier in some cases, without worrying about plan interference.

Re:The Problem with F# Evangelism by pjmlp on Thursday August 17, 2017 @05:45AM (#15035164)
How do you suggest to make use of higher kinds in Blend?

Immutable records are already possible today in C#, even if a bit more verbose than on F#, plus EF code is anyway mostly generated.