Calling OO to increase coupling is a weird take in a world where React's "functional components" and similar patterns encapsulate their state and rendering pipeline.
Sorry, wrong word. I meant “complecting” but as no one outside of Rich Hickey’s talks will understand that I reached for the wrong word.
OO conflates data and methods, which makes systems harder to test, reason about, and debug, because functions are less pure due to the “hidden” internal state of an object.
It also encourages heavy constructs that can often be replaced with trivial data structures that are much easier to work with.
Let’s not get started on inheritance.
I think OO is widely discredited now, although I do see a few experienced programmers still using it.
Calling OO to increase coupling is a weird take in a world where React's "functional components" and similar patterns encapsulate their state and rendering pipeline.
Sorry, wrong word. I meant “complecting” but as no one outside of Rich Hickey’s talks will understand that I reached for the wrong word.
OO conflates data and methods, which makes systems harder to test, reason about, and debug, because functions are less pure due to the “hidden” internal state of an object.
It also encourages heavy constructs that can often be replaced with trivial data structures that are much easier to work with.
Let’s not get started on inheritance.
I think OO is widely discredited now, although I do see a few experienced programmers still using it.