←back to thread

.NET 10

(devblogs.microsoft.com)
489 points runesoerensen | 2 comments | 11 Nov 25 15:44 UTC | HN request time: 0s | source
Show context
nozzlegear ◴[11 Nov 25 17:14 UTC] 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 ◴[12 Nov 25 09:40 UTC] 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 ◴[12 Nov 25 09:59 UTC] 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 #
1. banashark ◴[12 Nov 25 19:10 UTC] No.45904656[source]▶
They killed off VB, which if I recall the announcement correctly, noted that it statistically had a larger user base (by Microsoft metrics) than F#. There are a number of companies relying on F# for critical operations and MS has some use of F# internally which I understand has no plans of replacement, which helps balance out the fear.
replies(1): >>45907233 #
2. nu11ptr ◴[12 Nov 25 21:47 UTC] No.45907233[source]▶
I was curious so I googled. Best I can tell it is still supported, but perhaps stagnant?