We included a message about compatibility issues because there are, indeed, compatibility issues. We’ve gone out of our way to very carefully ensure Glass functions well with RTB since there are several variants still around that have patches allowing it to still work.
oRBs’ approach is incredibly invasive and really not a good way to go about it. Instead of offering compatibility, all your add-ons are overwritten and their code changed? That’s not the right way to implement backwards compatibility and isn’t good for either developers or users.
Only a small percentage of users actually have oRBs (there’s maybe 5 online at any given time?) and we deemed it no longer worth our time to provide support that nearly mirrors RTB for an inferior product that’s both broken and very rarely utilized.
You get the oRBs compatibility message every time an unsupported method is called that’s going to cause some sort of conflict. Our preference manager doesn’t sync up with oRBs’ preferences, so every time a pref is registered through oRBs you receive that message. Making the message only appear once is ineffective for debugging or trying to figure out why your pref is only showing up in one or the other manager but not both.
There’s nothing about pettiness or personal preference here. I don’t lose sleep over “competition”. oRBs and Glass just don’t play well together and it’s not a significant enough issue for us to invest a lot of time in to addressing.