C++ ABI issues seem to be in this paradoxical situation where the language standard powerbrokers simultaneously feel that<p>a. Having a real binary compatibility story is beneath C++, but<p>b. The accidental ABI compatibility that exists today is too widely adopted to break.
Am I wrong in thinking that this mild form of schizophrenia ( no official ABI but dont break the ABI) is part of the reason why we now live in a world where all applications talk to each-other through sockets, incurring huge overheads?