4 ms·
It's a pretty simple explanation. Google talk was XMPP which is just not a good mobile protocol.
by jayd16 9y ago
It's a pretty simple explanation. Google talk was XMPP which is just not a good mobile protocol.
- donbox 9y agoCould not they just replace the XMPP protocol with whatever better protocol, while keeping the GTalk alive.
- delecti 9y agoThey kinda did exactly that. GTalk became Hangouts which is no longer quite XMPP.
- vijaybritto 9y agoIt's kinda sad how they ruined a superb product and replaced with something some par!
- orbitur 9y agoWell, not only did they change the protocol, they ruined the UI too.
- seba_dos1 9y agoX in XMPP stands for eXtensible. They could simply augment XMPP to match their needs better - and guess what, it's exactly what happened in last years. Now XMPP is a good, modern, battery- and UX-friendly IM protocol, with some clients even E2E encrypted by default.
- giancarlostoro 9y agoI had Google Talk on my phone for ages, I'm not getting what you mean by this. I had no issues. It was fast, to the point, and worked.
- mmcnl 9y agoI don't think lack of technical expertise to fix whatever needs to be fixed is what caused Google's demise in the messaging domain.
- PedroBatista 9y agoBy "not a good" you mean an open protocol not controlled by Google?
- izacus 9y agoNo, by "not a good" he probably means that it's not well suited for low battery consumption expected from a mobile device. Don't push your words on other people :(
- ralphm 9y agoThe battery argument is just misinformed. The real reason Google dropped XMPP was not a technical one. Yes, Google claimed it was not "cloud ready" at that GoogleIO. The same one where they announced Google Cloud Messaging, based on, wait for it, XMPP.
- stevenwoo 9y agoIIRC WeChat started from the ground up with a custom protocol designed for compatibility/efficiency with low bandwidth mobile networks for maximum reach, IMHO a great example of thinking outside the box of "let's use XMPP since it works".
- seba_dos1 9y agoMaybe it wasn't in 2006, but it wasn't that hard to make it a good mobile protocol and now it certainly is.
- SamWhited 9y agoWhat makes you say it's not a good mobile protocol? It had some problems in the early 2000s on mobile, but these days it has stream management similar to TCPs and XML compresses very well. As I mentioned in another comment, there are people running it over very low bandwidth HF radio, if it works well there it works well over phones, but I'd be curious to see why people still think otherwise. (Google Talk, naturally, never did implement any of the parts that make it good on mobile, just lilke they refused to do TLS on server to server connections, so note that I'm not arguing that Google Talk was good on mobile, just that if they'd worked on it a bit it could have been)
- jayd16 9y agoWhat service is using it at scale these days? I can't really think of a popular user. After a certain point it just becomes a headache. When I was working with ejabberd clusters servicing mobile clients it worked but I've had a lot less pain just using a custom protocol over websockets. My personal experience also seems to be mirrored throughout the industry as all the big players eventually move away from xmpp.
- wink 9y agoAll big players who have an interest in building a walled garden - yes, that sums up "all big players". GTalk was awesome while it was federated.
- rakoo 9y agoMost ironically, Google is using it for their Cloud Messaging solution (https://developers.google.com/cloud-messaging/ccs https://developers.google.com/cloud-messaging/ccs and https://firebase.google.com/docs/cloud-messaging/server#choose https://firebase.google.com/docs/cloud-messaging/server#choo... for the replacement) to allow applications to talk with a backend.. The advantages over HTTP are multiple: better battery life, bidirectional communication, asynchronicity. Riot Games is also using it for the messaging part of League of Legends (https://engineering.riotgames.com/news/chat-service-architecture-protocol https://engineering.riotgames.com/news/chat-service-architec...) XMPP is also used by military organisations such as NATO (https://www.isode.com/solutions/military-xmpp.html https://www.isode.com/solutions/military-xmpp.html) The sad truth about XMPP is that it just works, but it has a very bad publicity because there's just no marketing around it, and it's never used directly by users. So it suffers from that wrong image that is just completely outdated.