Another article which confuses class based programming with OOP.

At the author. As long as one deals with objects and in addition applies techniques which enable controlled access to such objects (encapsulation) and has methods as well which execute computations upon such objects one does OOP. "Class" is a concept which with establishing the OOP Paradigm was not part of it. OOP can be practiced perfectly fine without classes but not the other way around.

From everything said in the article it's title should be changed to ... Why I dropped Classes in Favor of Pure Data Objects and Functions in Full-Stack TypeScript.

The answer of cause is .. it's a special use case within the entire tech-stack, where one just needs to organize data in order to shovel it forth and back, which does not necessarily rely on complex abstraction layers.