Drawbacks of developing ASP.NET and ASP.NET MVC apps in F#?

Question

I would like to try developing ASP.NET and ASP.NET MVC apps in F#. I enjoy using functional langauges, and to my mind the functional paradigm fits better with H

Answer 1

Personally I am a big fan of F#. My NDjango parser/rendering engine is written in F#.

But trying to do everything in F# can be difficult. To add to your list of the things which are not there yet:

• There is no support for visual designers - neither webforms nor winforms. You can write the appropriate code manually, of course

• No Code Completion

• Debugging in F# can be a challenge, in particular because of anonymous closures

• Compiler Diagnostics can be misleading because of type inference - one typo can have profound impact in far away places

• My biggest pet peeve is the 'file order matter' rule. You have to specify the order in which the files will be compiled

By no means this is a complete list. On the other end one might hope that some of these points will be addressed in final release.

Despite of all of the listed (and unlisted) problems I enjoy programming in F# - sometimes it gives a very refreshing perspective on the coding and I already started using some of the tricks inspired by F# in my C# code.

Just do not go crazy in it