> as is any idea of "game-engine" code in C++ (as the post I replied to mentioned) Huh? That post only mentioned component and property systems as a possible u

> as is any idea of "game-engine" code in C++ (as the post I replied to mentioned) Huh? That post only mentioned component and property systems as a possible use case for reflection. I didn't see anyone proposing to add such systems to the standard. > And 100% out of scope of C++, like the std::thread?? No, threading is definitely in-scope. I would agree that networking should be in the standard library (they have been trying for years now). These things have a pretty well-defined scope. GUI libraries, on the contrary, tend to be massive and also rather opinionated. There is no single widely accepted GUI paradigm that could be standardized.