5 ms·

I disagree. I tried to learn F# a few months ago and the experience was horrible. I followed the tutorial using the aspnet CLI tool and got nothing but errors.

• jdc 6y ago
  Can you link to the tutorial you followed?
• tasogare 6y ago
  Of course it’s gonna be hard if you are trying to learn a language plus a framework at the same time, especially given that F# is treated as a second class citizen by Microsoft. An easier path is to break that learning into more manageable tasks: on one hand getting familiar with F# (which is already some work as it has both a functional side, and a CLR one; you need more the OOP part for doing ASP.net) and in the other ASP.net, for which the golden road is C#. Otherwise the doc is quite good for ASP.net Core, and it’s rare I get stuck on a problem for too long with it.
• rumanator 6y ago
  > I tried to learn F# a few months ago and the experience was horrible. Switching to a programmig language based on an entirely different programming paradigm is not comparable to switching to a language based on the exact same programming paradigm to develop the exact same application using the exact same design patterns.
  • turtlebits 6y ago
    I’m completely comfortable with the language coming from Elixir. The problem was the tooling/docs didn’t match the experience. This was from the official site and many of the commands threw errors. I think it was a case of incomplete Mac support, which should have been called out. IIRC I posted on HN about it and got an apology for the state of tooling