Hacker News Reader

Considering that the article is from 2012, it "went" a long time ago.

OOP is not idiomatic F#. It is mostly for interop with C#.

I would not say that, sometimes it's quite powerful to combine these paradigms. I think they would not design a language for CLR only to force them to create a huge interop subsystem.

You are right, however, that OOP should not be the default way to write things in F#.

I definitely appreciate being able to drop into an OOP style when I find it's necessary. In a talk Don Syme (F#'s original designer) goes into aspects of OO he enjoys, those understands the usefulness of, and those he does not enjoy. I believe it was F# Code I Love, which gives some good insight into the thinking behind the language.

Not true. You actually are not to use OO in F# unless you really have to and there are certain cases where it helps

F# is a pragmatic dual paradigm language where both OO and FP are fully supported and encouraged. There is no "[don't use OO in F# unless you really have to]" sentiment anywhere.