4 ms·

Since we're in here talking about all kinds of F# goodies, has anyone spent time with https://wiz.run/ https://wiz.run/?

by icey 5y ago

devmunchies 5y ago
Story on Wiz is since I’m a growth engineer I tend to think about usage on a more psychological level (optimizing for reduced friction and simpler onboarding). I found that most libs in F# have the .net APIs right in your face so users need to learn both. (E.g. I would define route handlers in the http library but if I want to change the server port I have to look at dotnet docs.) If F# is to be successful, I think more attention needs to be made to build abstractions on .net APIs.
pharmakom 5y ago
I briefly poked around the source code. I would pick Suave over Wiz since Suave has an immutable data model internally. If for whatever reason Suave is not fast enough, Giraffe can be fine tuned. However, it also exposes much of the underlying ASP.NET stuff. I love the website for Wiz though!
- devmunchies 5y ago
  yeah wiz is still a work in progress. Its mainly just trying to be a simpler API wrapper for asp.net Would challenge the notion of immutability or extensibility being a primary motive for using a library. Would like to see UX (DX more specifically) start to take more of a front seat in F#, since its one of the more neglected parameters of success in the ecosystem. Extensibility can be added, UX is more difficult to retroactively account for. If Wiz only influences other libraries to become simpler for new users then I will consider it a success. I just want more eng teams to use F# or Ocaml without having to justify why you aren't using python/node.js.
  - pharmakom 5y ago
    I admire and share this goal! However, if you translated the Wiz examples to Suave, would they be any more difficult to read? I think the biggest issue is Suave’s docs etc.

4 ms·

Since we're in here talking about all kinds of F# goodies, has anyone spent time with https://wiz.run/ https://wiz.run/?

by icey 5y ago

Since we're in here talking about all kinds of F# goodies, has anyone spent time with https://wiz.run/ https://wiz.run/?

devmunchies 5y ago
Story on Wiz is since I’m a growth engineer I tend to think about usage on a more psychological level (optimizing for reduced friction and simpler onboarding). I found that most libs in F# have the .net APIs right in your face so users need to learn both. (E.g. I would define route handlers in the http library but if I want to change the server port I have to look at dotnet docs.) If F# is to be successful, I think more attention needs to be made to build abstractions on .net APIs.
pharmakom 5y ago
I briefly poked around the source code. I would pick Suave over Wiz since Suave has an immutable data model internally. If for whatever reason Suave is not fast enough, Giraffe can be fine tuned. However, it also exposes much of the underlying ASP.NET stuff. I love the website for Wiz though!
- devmunchies 5y ago
  yeah wiz is still a work in progress. Its mainly just trying to be a simpler API wrapper for asp.net Would challenge the notion of immutability or extensibility being a primary motive for using a library. Would like to see UX (DX more specifically) start to take more of a front seat in F#, since its one of the more neglected parameters of success in the ecosystem. Extensibility can be added, UX is more difficult to retroactively account for. If Wiz only influences other libraries to become simpler for new users then I will consider it a success. I just want more eng teams to use F# or Ocaml without having to justify why you aren't using python/node.js.
  - pharmakom 5y ago
    I admire and share this goal! However, if you translated the Wiz examples to Suave, would they be any more difficult to read? I think the biggest issue is Suave’s docs etc.