Is it true that the signal and slot mechanism is trying to make up for the shortcomings of the architecture?

Question

Qt

When using C++, there are many frameworks (Qt, boost, ...) that implement the signals and slots mechanism in one way or another. However, this mechanism is not the simplest.
When used incorrectly, it smears the logic of the object's behavior. For example, instead of directly calling one method B from another method A , the called method B is bound to the signal sent at the end of the first method A .
On the other hand, signal slots allow fair message sending and multi-threading while hiding implementation details such as event loops and message queues.
What can you say for or against the use of signals and slots?

Answer 1

I speak from experience with Python and JavaScript. in some frameworks, there are also ideas similar to slots and signals, they have two convenient leads:
1. one event (signal) can have several handlers, this has already been called
2. the sender of the signal may not think about who will listen to it, and will listen at all