19 ms·

F# touches on most of these points doesn't it?

• weberc2 8y ago
  Last time I tried using it, it was unclear what build system to use and I had a hard time finding the "happy path" (what test library to use, how to set up my project file to include a test target, etc). It also seems to have this weird FP/OOP dichotomy where some things are methods on a class and others aren't and that affects how you call things and so on. I didn't get far enough to really be able to articulate my problem, but it seems quite complex (albeit much of the complexity probably exists to support interop with other .Net things). I think most of this could be addressed with documentation "How to do X in F#" (I'm sure someone has a writeup somewhere, but I couldn't find any such document around the time I tried it).
  • rs86 8y ago
    FP and OOP are orthogonal... You can have purely functional objects
    • phyrex 8y ago
      I fail to see how this would work. An object is a combination of state and methods acting on the state, and purely functional meaning no state.
  • McWobbleston 8y ago
    F# for fun and profit is an excellent resource
    • weberc2 8y ago
      Yeah, I remember trolling through those and I found them really useful and accessible; unfortunately I don't remember the details about why they didn't help me get over the hump (I'm sure if I stuck with it long enough I could have; I just have limited free time).
    • vram22 8y ago
      Seconded. It helped me clear up some FP concepts.