←back to thread

.NET 10

(devblogs.microsoft.com)
484 points runesoerensen | 1 comments | | HN request time: 0.226s | source
Show context
nozzlegear ◴[] No.45890001[source]
As a daily user of F#, I'm most looking forward to the support for "and!" in computation expressions. There are a few performance-critical pieces of code I can think of that are currently wrapped up in "Task.WhenAll" / "Parallel.ForEachAsync" that I'd like to extract back into "native" F# task computations.
replies(2): >>45898152 #>>45898201 #
cies ◴[] No.45898201[source]
I really like F# (as I like OCaml, Elm and Haskell); but I'm always afraid MS will kill it one day.

It helps that now most (if not all) parts of the stack are open source and run on Linux.

replies(2): >>45898239 #>>45898319 #
madarcho ◴[] No.45898319[source]
Where is this worry coming from? (I'm curious, not shutting it down)

I might be biased from having worked with production F#, but it feels more like functional is making its way into C#, as the general industry sees value in functional principles. So F# feels like its more here to stay?

replies(2): >>45898584 #>>45904656 #
azertify ◴[] No.45898584[source]
Doesn't it feel like the functional stuff is coming into C# so that F# can disappear? Pure speculation on my part but doesn't seem unreasonable.
replies(3): >>45898753 #>>45899526 #>>45905757 #
1. WorldMaker ◴[] No.45905757[source]
The C# team admits to looking at how F# features work, but also keeps trying to make it clear that C# doesn't have a goal of entire eating F#.

C# still doesn't see itself as a functional programming language, even as it has added so many features. It may never get first-class currying or the broader ideas like generalized computation expressions, for instance. It certainly won't get F#'s cleaner syntax with fewer mandatory semicolons and whitespace nesting rather than curly brackets.

F# probably isn't going to disappear for a lot of similar reasons that GHC (the Glasgow Haskell Compiler) didn't disappear when F# was started (nor when key contributors left Microsoft). F# often already sees more outside open source contributors than contributions from Microsoft employees.