I kind of agree and also prefer to use objects in some cases.
F# is a functional-first programming language that comes with a substantial object-oriented feature set. It is so feature-complete in fact, that almost any C# class can be ported over to F# code with little substantial alteration.
However significant, this subset of the language is seeing limited appreciation from the community, which I suspect is partly fuelled by the known criticisms of OOP and partly by a desire to be different than C#. After all, this is a functional-first language so we can just replace all our classes with functions. There is also the opinion that OOP in F# merely serves as a compatibility layer for .NET, so it’s really only there to cover those unfortunate scenarios of having to use a library that accepts interfaces.
One of the most important aspects of maintaining a nontrivial codebase is controlling complexity. Complexity can be contained by partitioning code into logically…
View original post 1,596 more words
2 thoughts on “Why OO Matters (in F#)”
Hi all, here every person is sharing such knowledge, so it’s nice to read this website,
and I used to pay a quick visit this weblog
all the time.
Thanks to this article I can learn more. Expand my knowledge and abilities.