2
n1cK1337
129d

OOP is all about code reusability until you really want exactly the code Foo with non-pure functions in all your classes. You end up almost rewriting all subclasses' properties into the superclass to silence typecheckers. Is there no "I know what i'm doing, please just transpile/compile this piece of logic into these 20 places I need?" You end up doing it the functional way, dumping refs and params into some shared util function and have it do the job. I know, might as well have that one inherited also, but what's the point of adding more mess just for that ?

Comments
  • 2
  • 4
    @donkulator > "What?"

    I think it's a reference to the O-O purist mindset that doesn't always scale over time to an ever changing code base and business requirements. Like TDD, Agile, etc, O-O is often the golden idol devs sacrifice themselves without knowing why.

    I think he found if he started with a more functional approach, the changes would have been easier to implement.
Add Comment