From what I can understand, all the arguments seem to derive from some grumpy old curmudgeon who took a passing glance at Qt 15 years ago, without actually unde

From what I can understand, all the arguments seem to derive from some grumpy old curmudgeon who took a passing glance at Qt 15 years ago, without actually understanding what it is or does, and said "Why do I need this thing? I don't like extra stuff because 'reasons'. Its better if I reinvent the wheel myself. Preprocessors are always bad. Now get off my lawn!" Moc was introduced at a time that C++ really did not have the built-in features necessary to create a framework like Qt. Since then, a few things have happened. First, C++ itself has (very) slowly gained some of those features. Second, the Qt developers have found additional things they can do by having the "moc" tool integrated into their build processes, and thus have expanded its scope. But even if a day comes that Qt can totally get rid of "moc" in theory, in actuality there will still be a lot of people who actually need to use C++ compilers that still haven't implemented whatever new version of the standard accomplishes this.