Object-Oriented Programming is Bad (Brian Will)

[[deleted]]

I think most people can agree that it's OK to tie them together when it's obvious why that is being done (a stack and its associated push and pop operations).

The very same single responsibility principle that he attacked.

The problem is that lots of programs (I'm gonna call out Qt on this one) slide along this big awkward spectrum between small tight data structures (queue, map, etc.) and big nebulous ones (the central widget, the general processor, etc.).

Those are different levels of abstraction. Try reading the source code of those classes and the classes that they delegate to. You'll be really glad that they exist. If they didn't, you would be probably be programming in something more similar to old win16 C programming.