You can do that in C#/F# too. There's nothing special about Scala from this point of view.
You can do that in C#/F# too. There's nothing special about Scala from this point of view.
Last I checked you could not mix the two easily [0]
[0]: http://stackoverflow.com/questions/14280001/why-cant-we-use-...
PS And the linked question only describes the limitations of Visual Studio where you can have only one language in a given project.
Yeah just like C++ or Java now have "functional features". That doesn't make them functional languages, they don't promote functional programming to the extent that Scala does.
Aside from that, their type systems are much too unexpressive to allow for the style functional programmers are used to, not to mention they promote mutability.
Having lambdas makes you about as functional as C++ these days.
Functional/non-functional is a fuzzy distinction but C# is definitely not a functional language.
If it wasn't for nerfed imperative collection classes (to encourage functional solutions) in the standard library, you could totally just ignore the fact that Scala was a functional language at all; it is not in your face about it like Haskell.
It would probably be more correct to say that "Scala is the only language that does both FP and OOP very well." On marrying the paradigms....why not just use both as needed anyways? That is completely doable in C# as well, just not as well as in Scala.