3 ms·
This was posted to the cpp sub-reddit. The wacky non-standard license and the denouncing of modern C++ are large red flags, as well as vague terms like 'Object
by CyberDildonics 8y ago
This was posted to the cpp sub-reddit. The wacky non-standard license and the denouncing of modern C++ are large red flags, as well as vague terms like 'Object Request Broker' and custom implementations of standards.
To be fair though, the custom implementations of standards could be very useful if they can be made free of dependencies.
- Someone 8y ago”vague terms like 'Object Request Broker'” That’s more dated than vague, IMO. See https://en.wikipedia.org/wiki/Object_request_broker https://en.wikipedia.org/wiki/Object_request_broker.
- DeanRoddey 8y agoThe ORB is incredibly powerful. There's good video on it on my Youtube channel that demonstrates what it can do. And the related IDL compiler also allows for very powerful enumerations, far beyond what C++ itself offers. One reason ORBs have never caught on in C++ is exactly because there's no comprehensive, monolithic framework. It only works really in those scenarios. When you have such a thing, then any class that supports the binary streaming mixing can be passed back and forth to remote ORB calls. It's at the foundation of the CQC layer which has MANY complicated client/server interfaces. Without the ORB they would be a massive PITA. With it, they are quite manageable.