I assume that F# developers bring better business outcomes.
I am both a C# and F# developer, and in my experience functional code (F#, OCaml etc) tends to be 5 times less buggy than an imperative equivalent. F# compiler does an impressive job of catching errors at compile time: this is the primary reason for better outcomes. The second significant contributing factor: functional code tends to have less side effects, and thus developers can reason about such code more realistically.
A third contributing factor is lazy computations. Which leads to (surprise, surprise) better overall performance at runtime.
Less bugs + Better performance = Higher salary
Though I don't say F# is perfect. It has its quirks and there is a lot of room for future improvements.
Agree so before jumping into learning F# keep in mind it does not go that way "Know F#" -> "high paid job". It is more probable that those guys were already in place where F# was useful so they started using it as best tool for the job. So they were already highly paid.
On that note: Anyone know of any good F# learning resources (preferably books/text) for an experienced C# developer who has only done a little bit of functional programming (Haskell, Clojure) here and there?
I am both a C# and F# developer, and in my experience functional code (F#, OCaml etc) tends to be 5 times less buggy than an imperative equivalent. F# compiler does an impressive job of catching errors at compile time: this is the primary reason for better outcomes. The second significant contributing factor: functional code tends to have less side effects, and thus developers can reason about such code more realistically.
A third contributing factor is lazy computations. Which leads to (surprise, surprise) better overall performance at runtime.
Less bugs + Better performance = Higher salary
Though I don't say F# is perfect. It has its quirks and there is a lot of room for future improvements.