Hacker News Reader

Comment by amelius | Hacker News Reader

> it means that everything will more or less work with your code

So you can call any .NET library?

Not quite, it's a middle ground, https://fable.io/docs/dotnet/compatibility.html Blazor, (or Bolero as an F# friendly extension) compiles to WASM to run any .Net library.

In practice you occasionally find something that doesn't quite work, for the most part things related to IO and the TPL but I occasionally run into some more niche functionality with Date & time for example.

You can use most of the core F# library and some non fable centric libraries (e.g. FSharp.UMX of FSToolkit.ErrorHandling) work just fine.

I find it mostly a non issue, as any IO you want to go through the browser API instead or it's not supported. It didn't take take long at all to easily slip into the "I'm in the browser now" mindset.

by "everything" I think GP is referring to the JS ecosystem

Ok. Wouldn't it make more sense to compile .NET bytecode to JS?

Not necessarily. Aside from being more technically challenging, it's more of a "what are our goals" kind of question. Do you want to give F# developers who are afraid of javascript a way to avoid it altogether, or a way to bring those developers into the javascript ecosystem?

I've never dealt much with transpiling to JS, but I would guess that it's a lot easier to do it from the AST or some other higher-level intermediate representation than it is from CIL instructions. That way you don't have to fuss with programmatically figuring out what stack manipulation instructions are trying to accomplish or any other target-specific noise like that.

Fable has easy interop with JS libraries because it compiles to JS.

Reply on news.ycombinator.com