News for hackers. Stuff that matters.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by pmoriarty on Tuesday March 21, 2023 @06:19PM (#35253476)
As a fan of O'Caml, I have to ask: what's the status of F# on .NET?

...and is it used much compared to C#, or at is its use at least growing, or is it stagnating/dying?

Re:Understanding the .NET ecosystem: The evolution of .NET i... by pavelbr on Tuesday March 21, 2023 @06:38PM (#35253693)
Seems to be about the same as it's ever been. Still being updated and worked on, and still very few people use it.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by pyjarrett on Tuesday March 21, 2023 @06:45PM (#35253771)
> Still being updated and worked on

It is, hands down, my best experience working in a functional language. I do hobby work in it, and it seems super nice, but I'm not sure where everyone is.

> still very few people use it.

Looking at a chart of GitHub and StackOverflow usage[1], OCaml/F# seem almost steady compared to the other functional languages, my suspicion is that Rust absorbed a lot of programmers looking for functional concepts in programming languages.

[1]: https://tjpalmer.github.io/languish/#y=mean&weights=issues%3...

Re:Understanding the .NET ecosystem: The evolution of .NET i... by evntdrvn on Tuesday March 21, 2023 @07:19PM (#35254190)
yeah I’d say usage has been steady, maybe with a slight uptick in interest it feels like.

It’s a great platform, in some ways it’s like a secret weapon…

I joke that F# is kinda “easy-button Rust” lol

Re:Understanding the .NET ecosystem: The evolution of .NET i... by gaelian on Tuesday March 21, 2023 @06:47PM (#35253807)
I have a side project where, for some years now, I've supported an app built using F# with Xamarin.Forms and the Fabulous MVU framework. Before .NET 6, things were generally pretty great, and I thought this was an impressive achievement considering how many moving parts the combination of .NET with F# + Xamarin + Fabulous entails.

As .NET 6 and MAUI started to come on the scene, stuff went haywire pretty badly, tooling issues like breakpoints in Visual Studio no longer working in my projects, obscure build errors, confusing build warnings, dependency hell particularly with Xamarin.Android NuGet packages and Xamarin.Essentials. I'm still not up to date with all NuGet packages because doing so breaks my app at runtime. I'm in this halfway point in regards to use of the PackageReference project type. Things haven't been smooth lately for F# and Fabulous projects.

Things are slowly getting better though, and I would say that my experience is probably not entirely typical due to the inclusion of Xamarin, which introduces a whole additional layer of crazy. I think if you were to use F# for backend web services for example, then your experience would probably be a great deal more palatable than mine. I don't think F# is stagnating or dying by any means, but I do feel that it is still a second class citizen to C#. I hope MS continues to work towards this not being the case, because with all the "batteries included" of .NET behind it, I think F# is a great functional-first language.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by andix on Tuesday March 21, 2023 @08:04PM (#35254685)
F# works, it gets updates and there is good (not perfect) tooling. Everything you can do with C# can be done with F# too. Although most APIs don’t feel very natural in F#. F# has only a small ecosystem, so you may not find the right library for every task, and need to use something object oriented from the C# world instead.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by davidgl on Tuesday March 21, 2023 @08:06PM (#35254695)
My experience is good, small but very active and engaged community, interop with C# is seemless, I architect a large healthcare care system, 5% F# and 95% C# and very happy
Re:Understanding the .NET ecosystem: The evolution of .NET i... by keithnz on Tuesday March 21, 2023 @09:25PM (#35255464)
the core F# language is great, however, what tends to suffer is the F# specific libraries (you can use all .NET libs, but I'm talking about the F# specific ones) and community. There are some things that are getting developed, but my experience is that things get abandoned, progress is slow, or things are somewhat clunky. But if you are writing your F# without any need for F# specific libs then it is great and you can interface it with C# code easily.