It would be nice if you could print something with it. And "Fragile Base Class as a Service" isn't really the road to riches they thought it was in the 90s. T

It would be nice if you could print something with it. And "Fragile Base Class as a Service" isn't really the road to riches they thought it was in the 90s. Though I guess we replaced the fragile base class problem with the initialization fiasco and trying to figure out how to compile two different versions of boost into the same executable because you have two dependencies which depend on different versions of boost. In other words... C++ is great for closely coupled systems and services. But in many ways, application environments running on top of operating systems are more loosely coupled. Earlier versions of BeOS did not make it easy to run an app compiled for an earlier OS API to run on a machine with a later OS API without being re-compiled. That's not too big of a deal with Linux since many things are trivial to recompile. But BeOS was supposed to be a commercial platform and they were releasing a new version of the OS every 6 months. So if you wanted your software to run for people with an installed base and new customers, you had to maintain multiple versions of the same code for different minor revs of the OS. I'm not the biggest fan of the GNU Objective-C compiler (I cut my teeth on the full-function stepstone version), nor am I a fan of Mach (a heavyweight microkernel) or the son-of-NeXTStep monstrosity that is Rhapsody/macOS (with it's spinning beachball of death), but they did sort of figure out how to make late binding between applications and OS services work.