News for hackers. Stuff that matters.
Re:Update to the .NET Language Strategy by bmitc on Wednesday February 08, 2023 @06:48PM (#34717482)
> F# explores new language possibilities and the community provides a rich experience across platforms.

There are several interesting observations to be had here. For one, F# already explored (past tense) new language features and has long been essentially feature complete. It gets little features here and there, which are generally quality of life type of things (like anonymous records, for example).

Another interpretation is that F# is just viewed as a .NET/CLR playground and prototype lab to bring features into C#. This is already a common sentiment, but it looks like Microsoft just came out and said it here.

I'll need to read their full strategy, but the blog post is just the same old story: C# is everything, we'll limp along F# with the community doing most of the work, and, oh yea, Visual Basic.

I read through the F# strategy documents, and there's not really anything of substance there. I'm also not sure it's in F#'s best interest to be forced to comply with new C# features (of course F# needs to adopt new .NET features though). F# already does not support several C# features, for good reason, maintaining only what it needs for interoperability purposes. This just furthers the idea that F# is C#'s playtoy.

It's all unfortunate. F# is one of the best designed modern languages around. I wish people would embrace it like Elixir has been embraced. F# could truly be one of the more popular languages and doesn't have to be used at just ".NET shops".

Re:Update to the .NET Language Strategy by justin66 on Wednesday February 08, 2023 @07:37PM (#34717992)
* * *
Re:Update to the .NET Language Strategy by bmitc on Wednesday February 08, 2023 @08:34PM (#34718538)
I'm not sure about that given the amount of jobs I have had and found in Elixir, which also has a more vibrant ecosystem. I have strong confidence that I could get another Elixir job. I would be surprised if I could even locate an F# job.
Re:Update to the .NET Language Strategy by justin66 on Thursday February 09, 2023 @01:40AM (#34720485)
* * *
Re:Update to the .NET Language Strategy by andsoitis on Thursday February 09, 2023 @05:25AM (#34721965)
a quick search on indeed.com reveals 78 elixir jobs (https://www.indeed.com/q-Erlang-Elixir-jobs.html) and 426 f# jobs (https://www.indeed.com/jobs?q=F%23)

I’m sure some false positives, but I doubt enough that brings the F# count lower than that for Elixir.

ymmv

Re:Update to the .NET Language Strategy by BenGosub on Wednesday February 08, 2023 @07:10PM (#34717705)
They should release a roadmap, instead of this bland talk about strategy.
Re:Update to the .NET Language Strategy by mastax on Wednesday February 08, 2023 @07:49PM (#34718124)
Re:Update to the .NET Language Strategy by cglong on Wednesday February 08, 2023 @07:50PM (#34718132)
> F# already does not support several C# features, for good reason, maintaining only what it needs for interoperability purposes.

Could you enumerate some of these? My team is still using .NET Framework, so we're missing out on the new C# goodness.

Re:Update to the .NET Language Strategy by bmitc on Thursday February 09, 2023 @12:04AM (#34719987)
One is that C# has partial classes but F# does not. This comes up for all the XAML tooling that C# supports but F# doesn't. Also, F# only has null for use in certain situations only for interoperability. There are others that I've seen but don't know off the top of my head. I think they are usually OOP related and at the edges. I don't much know them because I don't really know C#.
Re:Update to the .NET Language Strategy by pharmakom on Thursday February 09, 2023 @03:39AM (#34721246)
AsyncDispose is one more, IIRC
Re:Update to the .NET Language Strategy by pjmlp on Thursday February 09, 2023 @02:10AM (#34720673)
And if you go for the comments, the confirmation that C++/CLI is also managed by WinDev, not DevDiv (which owns .NET).
Re:Update to the .NET Language Strategy by pharmakom on Thursday February 09, 2023 @03:38AM (#34721243)
F# has a bright future, but it’s due to Fable and breaking free of .NET.

F# is truly a full stack language now.

Re:Update to the .NET Language Strategy by pjmlp on Thursday February 09, 2023 @08:34AM (#34723641)
Latest the F# folks tried to pivot the language into data science and be a safer alternative to Python, only to have Microsoft hire Guido and being the company that finally managed to push the CPython devs to focus on performance, and JIT integration.
Re:Update to the .NET Language Strategy by rfreytag on Thursday February 09, 2023 @12:02PM (#34727125)
I think F# is going to do well because it is driven by the community making it an open field despite being .NET. F# developers seem to have a higher than usual lower-bound.

Elmish.WPF, FParsec, so much there and still things to do...like better development tooling with VS Studio Pro.

If it were a sure thing it wouldn't be a challenge or quite as interesting.