4 ms·
Google has said that it was a difficult decision necessitated by new technical demands. But even if this new protocol responds to different technical requiremen
by shmerl 14y ago
Google has said that it was a difficult decision necessitated by new technical demands. But even if this new protocol responds to different technical requirements, that shouldn't prevent the company from making it public and interoperable.
Well said. Google made a bad move with breaking things before enabling interoperability by publishing their protocol. It's not the proper way of doing things. Firstly, they could extend XMPP, Jingle etc. instead of creating something from scratch.
If they can't (though they didn't explain why), they need first to develop a protocol, publish it, and then start deploying it. Not other way around! Right now they are moving towards cutting the connection between Google users and users of other XMPP servers. Connection which works already now. I can understand that they might envision new communication patterns, but it doesn't mean one has to break what already works before enabling others to interoperate. It's completely immature on Google's part. Going the right way might take more time - but it will not increase the horrible mess that the IM scene is today. What Google does now is creating only more mess.