F#

So anyway I have begun my foray into F#.  Because I plan to use .net in my next project I think it will be fun to learn F# in addition to C# and use both languges in the project.  To this end I just ordered Expert F#.  Knowing /prog/ is infinitely more expert then me: 

what does /prog/ think about .net?
what does /prog/ think about F# (ocaml)?
What type of tasks are better to be performed in F# vs C# (Math type tasks heavy)?

>>35
It's not portable. Period. The reason comes back to the whole Microsoft thing, but not in the way that you might so casually brush off as Microsoft-hatred. It's because they control the specifications and write them with their own interests in mind -- regardless of how well-designed the .Net platform is, it's still written by one single proprietor targeting one OS family (Windows), and many of the design decisions they made reflect this. Even if a third party creates a .Net implementation for some other OS, it's not going to get first-party support and won't affect the decisions MS makes in the future.

It's a good platform but fundamentally unsustainable for cross-platform development. This is why people make independent design groups for these things -- to keep any one vendor's interests from clouding the overall design with decisions specific to their own implementation.