How well are F# and C# supported on the Linux platform?
Update to the .NET language strategy
11–20 of 151 posts
Re: Update to the .NET language strategy
#122022 I started a new job where we mainly use C# and I have to say, this is my favorite language now, especially with Visual Studio and Reshaper. I've never felt so productive and at ease while coding!
Rider is even cooler, with all the magic from ReSharper, and the much saner IntelliJ user interface.
Re: Update to the .NET language strategy
#13TLDR: C# is our real language. F# is a thing that gets supported to the extent that unpaid volunteers do the work. VB is in back-compat legacy support mode.
Huh?
F# has Microsoft Research building it and its libraries and optimizing compilers, no?
Re: Update to the .NET language strategy
#14How well are F# and C# supported on the Linux platform?
First class. I would wager that most new .NET projects are primarily targetting Linux for deployment.
Re: Update to the .NET language strategy
#15Re: Update to the .NET language strategy
#16How well are F# and C# supported on the Linux platform?
I use both on Linux (and Windows, and MacOS) and they're excellent.
Some libraries thought of as C# are bindings to Windows OS things, so those are platform specific.
You've really got to read the Microsoft Learn pages to get higher resolution for an answer, though.
Re: Update to the .NET language strategy
#17How well are F# and C# supported on the Linux platform?
C# support should be pretty good. You've got options. You can use the Mono ecosystem, including the MonoDevelop IDE, Mono runtime, and libraries like GtkSharp; these have been around for a while and some Linux desktop apps use it. You can also use the official Dotnet SDK and runtime, which lacks some stuff that Mono has for compatibility (like Winforms) but should have a good developer experience in either VSCode or Jetbrains Rider, and supports the latest .NET and C# features.
I don't know much about F#, but it seems F# isn't far behind. There's a useful page about getting started and other than the omission of Mono it is similarly supported.
Re: Update to the .NET language strategy
#18Sounds like Visual Basic will be a second-class citizen going forward.
Visual Basic had already become a second-class citizen fifteen years ago, when I worked on its compiler team. All the actual design work happened in the C# world, and our job was just to tag along and mimic whatever they had come up with. I had taken the talk of "co-evolution" at face value before going to work there, but after seeing where devdiv actually put its time and attention, that was clearly just a PR story…
> All the actual design work happened in the C# world, and our job was just to tag along and mimic whatever they had come up with.
What's the unique guiding philosophy or use case of VB that would justify developing bleeding edge new language features in VB first? Maybe I am just being overly critical here but I just don't see how the use cases which VB accommodates would benefit from getting new features before C# gets them, and the divergence would create unnecessary pain across the whole ecosystem
Re: Update to the .NET language strategy
#19How well are F# and C# supported on the Linux platform?
Great. Just install the .NET SDK, and you get both languages. You can start an F# REPL immediately after installing with `dotnet fsi`.
Re: Update to the .NET language strategy
#20How well are F# and C# supported on the Linux platform?
First class. I would wager that most new .NET projects are primarily targetting Linux for deployment.
Besides battling Visual Studio, `dotnet` cli and C# as a language, deploying a binary built on Windows to Linux was a breeze. If you're more used to the development environment, I bet it'd even be pleasant.