Well, OOP abstracts data, but to do it mutates many shared states across many functions, causing side-effects, breaking context of mutations, forcing to think about unpredictable order of mutations, etc., which leads to a tremendous amount of accidental complexity, hard to understand and hard to test code.<p>There is an inverse approach, that abstracts state mutations instead of data itself. Which means no more shared mutations, no more side-effects, no more breaking context of mutations, no more uncontrolled mutations, everything is in exact order it is supposed to be used, everything is easy to understand and easy to cover with tests, etc. And it&#x27;s just as flexible in Javascript, since it supports higher-order programming, but doesn&#x27;t lead to nearly as much accidental complexity. However, it&#x27;s not popular and not taught at schools, like OOP.