I've come to understand where Hangout's come from, and to appreciate its features. I say this as a longtime Jabber fan (yes, despite the XML-bloatishness that people complain about).
Hangouts is a more-featureful answer to the likes of Whatsapp, Facebook Messenger and Line. The global population has strongly switched to mobile chat apps. What does "online/away" mean when you can check your phone anytime, whether in the office, on the toilet, having lunch or dinner, etc? Sure, you might not be immediately able or willing to respond, but so what? Do you know anyone nowadays who actually expects an immediate response from a text message? Hangouts provides one discreet but useful feature previous chat systems didn't : did you ever notice the position of your correspondent's icon in the chat stream? That's how far they've read.
My main issue with Hangouts is that the delivery-reliability on mobile is poor. I've had messages arrive minutes, hours, up to half a day after it was purportedly sent. At least I know my correspondent hasn't seen it from the aforementioned icon feature... It happens often enough that I use Line whenever I want any guarantee of delivery on my/their phone. Despite the poor performance of that app...
Hangouts also provides a free and seamless way to do voice and video chat. It may seem common now, but prior to it only Skype was doing as good a job, and Skype didn't provide the group-video feature for free! Google had long before provided protocol spec and open-source libraries to implement this in other Jabber clients. The pickup was dismal, so it's understandable if Google decided to forge ahead alone with their own technological developments.
As for why they've abandoned the light GChat desktop app in favour of the Chrome-integrated plugin... Vanishly few people (at the scale of Google's users) care about that, and it provides Google the guarantee that their users are running the latest version of the app. The latter is an incredibly powerful incentive, because it means they can expect feature and bugfix rollout to happen quickly, and not worry about legacy support. If you've ever developed a long-lived distributed app, you know how tempting that would be...
I remain deeply disappointed that Google won't open the protocol, because it means users like us with the will and the means to build alternative implementations can't do so. I don't know what the state of reverse-engineering is for the protocol, but I figure that, being built on protobufs and with the fast-rollout mentioned above, this isn't a viable hope, unlike previous chat systems that had to support legacy versions of their protocol for a long time.
I keep powerlessly hoping that someday Google, or some other mobile chat provider, will open up their protocol for technical users to get crazy with. In the meantime, welcome to the post-Jabber world and here's your Koolaid.
It feels heartwarming and at the same time depressing to read this, which is point-perfect what I've been feeling ever since the release of Hangouts.
I too cross my fingers for the protocol to one day be opened up and properly specced up. I... I don't have much hope for it. I don't know. Google is usually pretty good on that front, but the hangouts team seems to be in its own bubble (please anyone prove me wrong for the love of entropy).
Jabber is perfect until it's not. I feel really bad about that. Maybe I let some things affect me too much, but the state of jabber today is something that truly haunts me. Messaging, communication, those things are some of the best and most important (at the scale of humanity) benefits the internet has brought us. And they are being closed down :(
> Hangouts provides one discreet but useful feature previous chat systems didn't : did you ever notice the position of your correspondent's icon in the chat stream? That's how far they've read.
SMS (1993), iMessage and Facebook Messenger all show what messages someone has read or not, even if the UI may be different.
Hangouts is a more-featureful answer to the likes of Whatsapp, Facebook Messenger and Line. The global population has strongly switched to mobile chat apps. What does "online/away" mean when you can check your phone anytime, whether in the office, on the toilet, having lunch or dinner, etc? Sure, you might not be immediately able or willing to respond, but so what? Do you know anyone nowadays who actually expects an immediate response from a text message? Hangouts provides one discreet but useful feature previous chat systems didn't : did you ever notice the position of your correspondent's icon in the chat stream? That's how far they've read.
My main issue with Hangouts is that the delivery-reliability on mobile is poor. I've had messages arrive minutes, hours, up to half a day after it was purportedly sent. At least I know my correspondent hasn't seen it from the aforementioned icon feature... It happens often enough that I use Line whenever I want any guarantee of delivery on my/their phone. Despite the poor performance of that app...
Hangouts also provides a free and seamless way to do voice and video chat. It may seem common now, but prior to it only Skype was doing as good a job, and Skype didn't provide the group-video feature for free! Google had long before provided protocol spec and open-source libraries to implement this in other Jabber clients. The pickup was dismal, so it's understandable if Google decided to forge ahead alone with their own technological developments.
As for why they've abandoned the light GChat desktop app in favour of the Chrome-integrated plugin... Vanishly few people (at the scale of Google's users) care about that, and it provides Google the guarantee that their users are running the latest version of the app. The latter is an incredibly powerful incentive, because it means they can expect feature and bugfix rollout to happen quickly, and not worry about legacy support. If you've ever developed a long-lived distributed app, you know how tempting that would be...
I remain deeply disappointed that Google won't open the protocol, because it means users like us with the will and the means to build alternative implementations can't do so. I don't know what the state of reverse-engineering is for the protocol, but I figure that, being built on protobufs and with the fast-rollout mentioned above, this isn't a viable hope, unlike previous chat systems that had to support legacy versions of their protocol for a long time.
I keep powerlessly hoping that someday Google, or some other mobile chat provider, will open up their protocol for technical users to get crazy with. In the meantime, welcome to the post-Jabber world and here's your Koolaid.