F# vs c# for an enterprise commercial project [duplicate]

This question already has answers here: Closed 12 years ago.

Possible Duplicate:

What are the benefits of using C# vs F# or F# vs c#?

So I started to catching on to the hype around the Microsoft's new functional language. After watching several video casts and playing around with it I really started liking the language. The type inference makes the source code look that much better than c#'s. But would you consider using F# to build a cla开发者_Go百科ss lib, for example, to call it from your c# code (asp mvc, wcf, etc)? Are their any caveats in doing so? Are there any advantages in introducing F# into a c# application?

---

F# syntax is lightweight, allowing to deliver more in shorter periods of time. I really like the async block and MailboxProcessor. These features are so nice that C# 5.0 tries to mimic and back-port them.

---

I've seen comments by people who do this and say that it has worked well for them, but the one thing you'll want to bear in mind is that there is a learning curve for C#/Java developers to become accustomed to F#'s functional programming model. So there will be an HR cost, as fewer people will be ready upon hiring to dive into the F# parts of your code.

---

i think there is if you want to do an application that has high level of transactions F# would help with that , plus you can make it as a DLL and use in a C# application

---

If your project would truly benefit being built on a functional programming language go for it. However this most likely not the case.

I would not recommend doing a full project in F# assuming you're talking about a network based enterprise software system.

If you feel there is a subsystem / routine that would greatly benefit from using F# by all means develop that part in F# and then bring it in as an assembly.