I was an Adium user for many years but frankly I very much disagree with Messages being bugridden, while assuming Adium is not. In fact Adium took so much work in trying to update it, logging me out randomly of AOL (and then telling me I am logged in on two devices), not showing things on MSN, not transferring images properly etc.
Much of the crappiness of Adium is a direct consequence of the crappiness of the protocol. MSN is particularly egregious - it is a protocol with almost no structure.
I've written (simple) MSN clients before, and the protocol (or what passes as one) is shocking. It's very clearly a protocol originally intended to exchange strings that has been overloaded with over 15+ years of new features and corporate strategies.
MSN support in Adium comes from libpurple, whose MSN support has always lagged behind the official client due to backwards-compatibility-breaking protocol changes, lack of documentation, and difficulty in reverse engineering. Frankly, I'm surprised MSN in libpurple works as well as it does.
File transfers (particularly MSN transfers) is also a crapshoot due to both bad, undocumented protocol design as well as the base technology. You're running into classic NAT issues that the protocol was never designed to take care of. Who you're sending to and what kind of router they're behind matters a lot.
tl;dr: MSN support in Adium sucks because the MSN protocol is awful.
• Having the client open for more than a few hours will use many gigabytes of memory (I'm at 2.5GB right now)
$ ps auxw |grep -i Message
jordan 73227 0.0 1.4 4037928 113476 ?? S 13Apr13 13:21.86 Messages*
I've had Messages open for 17 days now and it is using 111 MB of memory (that's RSS, VSIZE is 3.85 GB). I have 4 accounts (three jabber + iMessage).
I don't know much about your other problems. My biggest problem with it is that it doesn't reconnect always when I start/end my VPN sessions, but other than that seems to work ok.
You do have a point there. No doubt about it.
I should have written my comment differently. While yes, I do agree Messages has issues and launched prematurely (and hasn't been updated enough to fix all those issues), Adium has been out for many years and so many problems I've been having with it have never been addressed.
So - while yes, Messages is buggy, I'd say no Adium is not a more stable and productive replacement for it (in my humble opinion).
I think that might be where the difference is, it's the iMessage service simplimentation itself that is nasty — I've never used Messages.app to connect to AIM or Jabber.
Comments
I was an Adium user for many years but frankly I very much disagree with Messages being bugridden, while assuming Adium is not. In fact Adium took so much work in trying to update it, logging me out randomly of AOL (and then telling me I am logged in on two devices), not showing things on MSN, not transferring images properly etc.
Much of the crappiness of Adium is a direct consequence of the crappiness of the protocol. MSN is particularly egregious - it is a protocol with almost no structure.
I've written (simple) MSN clients before, and the protocol (or what passes as one) is shocking. It's very clearly a protocol originally intended to exchange strings that has been overloaded with over 15+ years of new features and corporate strategies.
MSN support in Adium comes from libpurple, whose MSN support has always lagged behind the official client due to backwards-compatibility-breaking protocol changes, lack of documentation, and difficulty in reverse engineering. Frankly, I'm surprised MSN in libpurple works as well as it does.
File transfers (particularly MSN transfers) is also a crapshoot due to both bad, undocumented protocol design as well as the base technology. You're running into classic NAT issues that the protocol was never designed to take care of. Who you're sending to and what kind of router they're behind matters a lot.
tl;dr: MSN support in Adium sucks because the MSN protocol is awful.
• Having the client open for more than a few hours will use many gigabytes of memory (I'm at 2.5GB right now)
• Messages aren't in chronological order
• Messages randomly shuffle depending on network conditions (this is the biggest issue)
• Messages randomly don't appear, appear late, or spam notifications on arrival
• "Deleted" messages aren't, so the /Library/Messages/ folder fills with junk over time
• The dock badge will sometimes be wrong, displaying a number when it shouldn't, or even showing negative unread messages
• You can render anybodies Messages.app useless with a bunch of unicode messages. They have to delete their databases and start over.
It's literally the worst application I've used, and you're the first person I've encountered that doesn't feel the same way.
• Having the client open for more than a few hours will use many gigabytes of memory (I'm at 2.5GB right now)
I've had Messages open for 17 days now and it is using 111 MB of memory (that's RSS, VSIZE is 3.85 GB). I have 4 accounts (three jabber + iMessage).I don't know much about your other problems. My biggest problem with it is that it doesn't reconnect always when I start/end my VPN sessions, but other than that seems to work ok.
* Edited so it would display nicely.
So I decide to try Adium again after reading this thread, and quit Messages:
You do have a point there. No doubt about it. I should have written my comment differently. While yes, I do agree Messages has issues and launched prematurely (and hasn't been updated enough to fix all those issues), Adium has been out for many years and so many problems I've been having with it have never been addressed. So - while yes, Messages is buggy, I'd say no Adium is not a more stable and productive replacement for it (in my humble opinion).
The only issue in the list above that I have experienced is the poor Library/Messages folder usage and that doesn't bother me at all.
I use Messages for everything and no longer use any other IM client - however - if Adium supported iMessage I'd totally go running back to the duck.
I think that might be where the difference is, it's the iMessage service simplimentation itself that is nasty — I've never used Messages.app to connect to AIM or Jabber.