How do Scala and F# compare when it comes to application development features?
developer.com
developer.com
I've been programming almost exclusively in F# over the last year - but they've been smallish projects. The weird thing about F# is that the code keeps collapsing from huge constructs down to really small pieces.
A couple of nits from both of this guy's articles. F# supports multiple inheritance through interfaces, which ain't C++ but it's good enough for government work. F#'s pattern-matching is freaking way far above the simple case he showed there: active patterns, assignment on test, structural-matching, etc. You can do some super cool stuff with F#'s pattern-matching. Hopefully he knew this and it was just an oversight.
Also he seems to indicate that MS is going to use F# as an entrance into large-scale scientific-type computing. This may be true, but it is badly misleading. By teaching developers to work with immutable data and functional composition, it opens up the entire PC stack to all sorts of improvements over your average VB code. I expect to see some really neat stuff come out along these lines.