Not quite, it's a middle ground, https://fable.io/docs/dotnet/compatibility.html https://fable.io/docs/dotnet/compatibility.html Blazor, (or Bolero as an F# fri

Not quite, it's a middle ground, https://fable.io/docs/dotnet/compatibility.html 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.