I'm no Google fanboy. But please reply to the argument instead of calling names. Resist complaining about being downmodded. It never does any good, and it makes boring reading. Please don't bait other users by inviting them to downmod you.
Instead of calling gmail "shit soup," just talk about the existing IMAP standard for keywords.
The whole concept of "don't complain about being down voted" is itself quite ridiculous. Given how hacker news works (i.e. down voted comments are hidden) this effectively encourages people to simply "go with the crowd". I disagree with this entire concept. Differences of opinion, and yes even criticism, are what drive people to make things BETTER.
> But please reply to the argument
What, like identifying why I believe Google's actions are "bad", what I think they could/should have done that would be "good", and how those alternative actions would have been had a more positive outcome?
Also, phrases like "about as much as I would trust a priest to give me a colonoscopy" and "the usual Google fanboy response" are inflammatory and inappropriate for substantive discussion, which is what HN calls for. Please edit such flamebait out of your comments. It's understandable that it sneaks in there—we're all susceptible to it—but that's what the edit button is for. Not only will excising it not hurt your argument, it will help it considerably, and display good manners to your fellow users to boot.
If you have a counter argument, reply.
Down voting a comment (which leads to it effectively disappearing) is the electronic equivalent of sticking your fingers in your ears and yelling "la la la I'm not listening" because you don't like what someone else said.
If someone posts a comment saying "I like chocolate ice cream" in a discussion about a new version of a piece of software, down vote to your hearts content.
When someone posts a comment that simply disagrees with your opinion, either ignore it or reply with a counter point.
And for the record, I don't have any opinion about this XMPP /Google thing. I don't even know what XMPP is, so I am perfectly neutral here.
Personally I trust that about as much as I would trust a priest to give me a colonoscopy - open access means less control for Google, which means less ability to collect data and/or display ads.
Keeping XMPP support (and federation) would have allowed interoperability with a range of XMPP clients on desktop/mobile devices, AND with users of other XMPP services - whether they be services provided by third parties, or "private" services run by organisations/individuals. It would also have also been useful as leverage to encourage other "big" IM networks to open up their "private" XMPP based IM networks - Facebook Chat, WhatsApp, Cisco WebEx, etc. They're all using XMPP, but they're islands right now. At this point Google are worse than those islands, because not only are they not embracing open XMPP & federation, they're not even supporting XMPP any more - so if FB/WhatsApp said "hey we want to support XMPP federation from tomorrow" Google users have no possible way to be involved in that any more.
Google's implementation of IMAP is fundamentally broken. The big ticket item, "tags" is ridiculous, as IMAP already has a defined standard for "tags": the IMAP keywords feature.
The usual Google fanboy response to this is "but IMAP clients don't support keywords fully", which of course ignores the fact that standard IMAP clients also don't support the idea of messages appearing in multiple mailboxes (i.e. folders) either, but the network effect of Gmail has meant MANY clients have come to support Gmail specific features.
Imagine for a second, if instead of its current shit soup solution, Google had implemented the existing IMAP standard for keywords. It's not unreasonable to expect that the majority of IMAP clients would have been quick(er) to implement support for this part of the spec, which would mean users of other IMAP services (either hosted services or self-hosted mail servers) would also be able to use IMAP keywords.
It's been said before and I'll say it again: Google is following the same plays that Microsoft made over a decade ago. Latch onto an open standard, use your market position to make "additions" to said standard, and finally pull support for said standard, in favour of your own closed solution.
I'll wait for the regular Google fanboy down votes.