4 ms·

I am curious whether you think F# is poor as a language for web/mobile development, or is it the F# tooling for such development that is lacking?

mamcx 10y ago
Tooling. And that some stuff (ie: c# centric classes) not interop as nicely (for example, expando objects, if I remember well...).
enricosada 10y ago
well, some options for mobile - xamarin works with f# and support it: https://developer.xamarin.com/guides/cross-platform/fsharp/fsharp_support_overview/ https://developer.xamarin.com/guides/cross-platform/fsharp/f... - use react native (with fable to transpile f# -> js): https://github.com/fable-compiler/fable-react_native-demo https://github.com/fable-compiler/fable-react_native-demo for web you can use: - suave (http://suave.io http://suave.io) - aspnet core (or aspnet core mvc) both works with .NET, .NET Core and Mono
- mamcx 10y ago
  I'm aware of all that options, and have tested them. In fact, I have tried to use xamarin+f# for mobile for a year. Now is a better (even have F# templates!) but is clearly a second class citizen. -- Is not the case of Core that F# integration is black magic, or this has changed in last release? All apis work now for F#? For web I try like 6 months ago and only suave was more or less usable (however, is hard to find how solve some stuff. NOTHING (in the open source options I test) is close to Flask/django in this case, and asp.net was sub-par when I test it.) -- I also agree that F# need more push from MS. My complaints, like much others, are about things that just need more polish and tooling - and if it get more competitive in performance with C#, better -. So I think is good to see this .NET strategy and think F# have a good future, to the point that F# is the only reason I come back to .NET. Is only, I wish not just a good future. I want a AMAZING future!

mamcx 10y ago

Tooling. And that some stuff (ie: c# centric classes) not interop as nicely (for example, expando objects, if I remember well...).

enricosada 10y ago

well, some options for mobile - xamarin works with f# and support it: https://developer.xamarin.com/guides/cross-platform/fsharp/fsharp_support_overview/ https://developer.xamarin.com/guides/cross-platform/fsharp/f... - use react native (with fable to transpile f# -> js): https://github.com/fable-compiler/fable-react_native-demo https://github.com/fable-compiler/fable-react_native-demo for web you can use: - suave (http://suave.io http://suave.io) - aspnet core (or aspnet core mvc) both works with .NET, .NET Core and Mono

mamcx 10y ago
I'm aware of all that options, and have tested them. In fact, I have tried to use xamarin+f# for mobile for a year. Now is a better (even have F# templates!) but is clearly a second class citizen. -- Is not the case of Core that F# integration is black magic, or this has changed in last release? All apis work now for F#? For web I try like 6 months ago and only suave was more or less usable (however, is hard to find how solve some stuff. NOTHING (in the open source options I test) is close to Flask/django in this case, and asp.net was sub-par when I test it.) -- I also agree that F# need more push from MS. My complaints, like much others, are about things that just need more polish and tooling - and if it get more competitive in performance with C#, better -. So I think is good to see this .NET strategy and think F# have a good future, to the point that F# is the only reason I come back to .NET. Is only, I wish not just a good future. I want a AMAZING future!