4 ms·

I find .NET Core (particularly ASP.NET Core with F# via Giraffe - https://github.com/giraffe-fsharp/Giraffe https://github.com/giraffe-fsharp/Giraffe) extremely

I find .NET Core (particularly ASP.NET Core with F# via Giraffe - https://github.com/giraffe-fsharp/Giraffe https://github.com/giraffe-fsharp/Giraffe) extremely good since Microsoft went all open source. I have multiple backends running in a GCloud Kubernetes cluster and develop all my stuff from a non Windows environment. Couldn't be more happy and the speed of ASP.NET Core with Giraffe is fantastic (~100K r/s).

dustinmoris 9y ago
I'd like to add that with F# you get all the benefits of an extremely mature web stack with asp.net core and a huge eco system of very high quality libraries. Frameworks like Giraffe, Suave or Freya make it all possible to write your backend in a functional idiomatic way. Also a big plus for F# is the choice of top notch tooling. You've got Visual studio which works on Windows and Mac, then JetBrains Rider which is awesome and Visual studio code with the Ionide extension. I'd highly recommend anyone to go and check it all out!
- xstartup 9y ago
  I am also leaning towards F#. What do you use for json serialisation? Any guide which describes basic steps to put together a web api.
  - EnderMB 9y ago
    JSON.NET is the standard library for handling JSON on the .NET platform, and to my knowledge it's available for both .NET Core and for use with F# collections. I've never used F# on .NET Core, but I'd be surprised if it didn't work.
    - edgarsanchez 9y ago
      Yep F#, the language, works all right in .NET Core 2.0. Some libraries, particularly, type providers, not yet, but they are working, on it. And JSON.Net also works fine on .NET Core.
      - vorotato 9y ago
        As I understand it type providers work with dotnet core code, provided you build the providers in mono. But yeah that's not exactly ideal.
  - edgarsanchez 9y ago
    This e-book http://products.tamizhvendan.in/fsharp-applied/ http://products.tamizhvendan.in/fsharp-applied/ should get you covered, Version II is just out :-)
  - bohszy 9y ago
    Chiron is what I've been using. I like it because it's simple which means I can understand it. Currently using it with fable elmish architecture, again because it's simple and i understand it.

dustinmoris 9y ago

I'd like to add that with F# you get all the benefits of an extremely mature web stack with asp.net core and a huge eco system of very high quality libraries. Frameworks like Giraffe, Suave or Freya make it all possible to write your backend in a functional idiomatic way. Also a big plus for F# is the choice of top notch tooling. You've got Visual studio which works on Windows and Mac, then JetBrains Rider which is awesome and Visual studio code with the Ionide extension. I'd highly recommend anyone to go and check it all out!

xstartup 9y ago
I am also leaning towards F#. What do you use for json serialisation? Any guide which describes basic steps to put together a web api.
- EnderMB 9y ago
  JSON.NET is the standard library for handling JSON on the .NET platform, and to my knowledge it's available for both .NET Core and for use with F# collections. I've never used F# on .NET Core, but I'd be surprised if it didn't work.
  - edgarsanchez 9y ago
    Yep F#, the language, works all right in .NET Core 2.0. Some libraries, particularly, type providers, not yet, but they are working, on it. And JSON.Net also works fine on .NET Core.
    - vorotato 9y ago
      As I understand it type providers work with dotnet core code, provided you build the providers in mono. But yeah that's not exactly ideal.
- edgarsanchez 9y ago
  This e-book http://products.tamizhvendan.in/fsharp-applied/ http://products.tamizhvendan.in/fsharp-applied/ should get you covered, Version II is just out :-)
- bohszy 9y ago
  Chiron is what I've been using. I like it because it's simple which means I can understand it. Currently using it with fable elmish architecture, again because it's simple and i understand it.