Comment by HarHarVeryFunny

> I used to use Qt quite extensively years ago, and it seemed that all MOC was really bringing to the table was signal-slot connections which can certainly be done in much nicer ways (e.g. just use std::function to represent signals).

The linked article goes into detail on what are the use cases for MOC and what are the shortcomings of C++26 to completely replace MOC with C++ reflections.

If you read the article, the goal they are aiming for is replacing MOC with C++ reflections without requiring fundamental changes to how Qt works. There are many reputable and very stable signal&slots implementations in C++ that are both type safe and do not require reflection at all. Some of these projects exist for over a decade already, and required only C++14. But Qt's implementations of signals and slots require far more than that to have a drop-in replacement.

That is what the linked article is about: what moc provides and what the pure C++ equivalent (if any) could be.

If you use QML it does, like... everything? QML can't interact with native C++ at all, you must use the MOC to generate Q_PROPERTYs, signal/slots, the Q_OBJECT macro itself etc.