He could try: - satisfying contracts using delegates/lambdas rather than interfaces - using higher order fn's rather than indexed loops, etc. which he's obvi

He could try: - satisfying contracts using delegates/lambdas rather than interfaces - using higher order fn's rather than indexed loops, etc. which he's obviously used to doing in F#, so he can do it from C# as well. If he rants on C# like this, I'd hate to say what he has to say about Java which, as someone said is not object-oriented but "class-orientated". It's hard to believe that D.S. wrote this -- esp. since C# has borrowed so much of F#'s ideas, and you can just write F# if you like, or use both. I've been using F# since it was first released, and it's great, but certainly not perfect either. IMHO, C# is one of the best all-around general-purpose languages with "familiar" syntax around with 1st class tooling and ecosystem. All it needs is records w/structural equality semantics, DU's and implicit "new" in object creation. F# on the other hand hasn't moved the it's needle much in a long time. (Like using Rosyln as a back end, supporting higher-kinded modules, etc.)