3 ms·
OO is all goodness, just like FP. But the way it is implemented by some people can make it impossible to easily understand or modify -- just like FP. OO is sim
by DanielBMarkham 18y ago
OO is all goodness, just like FP. But the way it is implemented by some people can make it impossible to easily understand or modify -- just like FP.
OO is simply organizing your code before/as you write it. Combined with UML, it can be a kick-ass way of describing your general strategy for dealing with complex problems. Or it can take something simple and make it into a monster -- it's up to you.
Another way of looking at OO is that you are building your own language as you go along by starting with nouns (types) and adding all sorts of verb-clauses to hook them together. You can do this in a super-cool, easy-to-understand way, or you can get a bit carried away and try to recreate the dictionary when you only need a few nouns and a few verbs.
OO's goal is not tight, beautiful, concurrent code. You want to feel like Picasso or Spock, go write FP.
For all of those reasons, OO just isn't as sexy as FP. You're not writing something that scales to a zillion users right out of the bag. You're not doing a lot of meta-programming, recursion, lambda calculus and such. You're not writing anything sneaky, clever, or bound to impress the other nerds. Everything just looks plain Jane. Add to that all of the examples of bad pattern usage and other atrocities in the OO world and I can easily see why other ways of doing things can seem more attractive.