free-vscode-csharp VS Fable: F# |> BABEL

I only tried F# for few days, but it was a pleasant experience on both macos and linux.

dotnet CLI should take care of build process, it can even generate self-sufficient executable (that bundle parts of .NET in them). The infamous required XML boilerplate has also been cut down to near-zero.

My biggest gripe is that Microsoft's debugger is closed-source and proprietary (though free for users of official VSCode builds). There is open-source netcoredbg by Samsung, so you can use VSCod[e,ium] with https://open-vsx.org/extension/muhammad-sammy/csharp , but YMMV.

When looking into C# tools though, my understanding is that the main debugging tool is under a proprietary MS license, although maybe I'm misunderstanding that. My question is, is there a FOSS debugger or tool kit for C# development? I did find this on the marketplace but am not sure if this is what I'm looking for. I know this is a bit of a niche case but was hoping to clarify. I'm not committed to VSCodium and am open to other text editors/IDEs, although would prefer to stick with it if possible.

My understanding is that I can install VSCodium and that they have many of the most popular extensions available. They even seem to have an alternative for the C# debugger. I could also use VSCodium and manually install the Microsoft extensions from the distributed VSX files.

and there is a VSCode extension that uses this instead of the MS debugger

https://open-vsx.org/extension/muhammad-sammy/csharp

C# language (powered by OmniSharp): Official C# language support. The extension is subject to this restrictive license because it uses Microsoft's proprietary debugger. The source code is available under a MIT license. See this comment in the C# extension repo for some discussion on this. There is an alternative version of the C# extension in the Open VSX Registry that uses Samsung’s MIT-licensed Debugger.

Yeah, Gitpod is pretty nice for what it is. Although it's worth mentioning that certain proprietary Microsoft extensions are licensed for use only in Microsoft distributions of VSCode, so they won't work in Gitpod. Most extensions do work, but Pylance, C#, C/C++ doesn't, to name a few exceptions. Although for C# there is a FOSS extension you can use instead and for C/C++ there is clangd.

I'm not very familiar with C# and .NET, so I can't help you with any specifics. But I do know that Microsoft actively prevent the usage of their proprietary extensions such as the one for C# in non-Microsoft distributions of VS Code, such as VSCodium. Although if you're using VSCodium, you've probably installed the alternative FOSS version of the C# extension, unless you've sideloaded the official C# extension?

For C# there is https://github.com/muhammadsammy/free-omnisharp-vscode for Python there is https://github.com/Microsoft/pyright (Pylance is the proprietary counterpart) for C++ there is https://github.com/clangd/vscode-clangd

If you want to stay FOSS, you can use this fork of the C# plugin which uses a free debugger: https://github.com/muhammadsammy/free-omnisharp-vscode

The download URL for the debugger seems to have changed, but the latest version of the extension should include a fix for that (see muhammadsammy/free-omnisharp-vscode#20).

This conversation could be referring to https://fable.io/

Other than that, the question is indeed strange and I agree with your statements.

NOTE: For larger codebases with more history it is likely that the Program.fs file will have a lot of orchestration and logic as well. given that it is often where everything clashes and starts, for example the Fable Entrypoint is in Entry.fs and it contains a lot of code. The best you can do always is to start at the bottom of the file and work your way up. Remember: Everything at the bottom uses what has already been defined at the top so there are no circular dependencies or random functions/types at the bottom that can trip you off, everything comes from the top!

I am a big fan of going with web components + plain (build-less) javascript whenever possible, so it is not surprising that I often favor things like the Fable Compiler, where I can target my F# code directly to javascript and be as close to the native JS experience as possible, both for interop concerns and for ecosystem integration.

Fable compiler - https://fable.io/

The F# community is very friendly (these sub-communities as well), and they have plenty of good issues/opportunities to contribute OSS work to across any skill level.

Phosphor isn't hiring right now, but we expect to begin a search for FE/interface engineers over the next few month. Email [email protected] for anyone interested.

Naturally I’d recommend using a better language such as ReScript or Elm or PureScript or F#‘s Fable + Elmish, but “React” is the king right now and people perceive TypeScript as “less risky” for jobs/hiring, so here we are.

Stuff like this: https://github.com/fable-compiler/Fable/issues/1822

It just seems like an incredibly ambitious project that appears to have very little equal but is mainly worked on by a handful of people but no corporate backing. I get the feeling that if you want to use it, you'll either be the only one doing what you're doing or among just a few people. I already use F# and feel this way about the core language itself.

F# is also part of the OCaml family, has a great to-JS transpiler (https://fable.io/) and F# code can also be used in .NET projects.

I have heard many good things about https://fable.io/ Fable converts F# code to JavaScript. There are currently 407 packages available for interacting with existing JavaScript packages and frameworks.