In Lion, Safari switched to the then-new WebKit2 rendering engine, which further separated page rendering from the main Safari application process. But there may be a rough patch, with Messages in particular, at least in the short term. I suspect that the server side of Messages and Mountain Lion's other network-connected applications will continue to evolve, perhaps even more rapidly than the expected parade of 10.8.x updates. And I may have the GM version of an application, but am I connected to the GM version of the server software? Advertisement
#Yahoo messenger for mac 10.8 software#
Even if the software on your disk is completely bug-free, it may still behave erratically if the service at the other end of the network connection is sending bad data, performing poorly, or not responding at all. This confusion is an inherent problem with evaluating software in a world of pervasive network services. Is this the fault of the Messages application itself, or the back-end iMessage service that it's connected to?
Some messages never seem to arrive, or arrive late. I'd like to say that the final version of Messages in Mountain Lion addresses all the problems of the beta, but I've still seen some strange behavior. It quickly gained a reputation as one of the buggiest pieces of beta software Apple has ever released. A richer notion of presence and availability is required across all platforms before the ubiquity of iMessage protocol support can transition from a periodic annoyance to a clear benefit.Ī beta version of Messages that ran on Lion was released back in February.
The fact that an application that can receive messages from one or more protocols is running on a piece of hardware has little connection with the current desirability of receiving such messages on that device. On the other end of the line, message recipients need more control over where and how they are available to receive iMessages. These can serve as proxies for message destinations (e.g., if you know that a friend runs AIM on his MacBook and Messages on his iPhone) but it's far from an ideal solution.Īnd really, doesn't Apple want us all to be using iMessage and iMessage alone in the future? (For new, young customers who have never had an ICQ, AIM, Yahoo Messenger, or Google Talk account, this may actually be the case.) In this situation, protocol selection is no longer a useful tool for controlling message targets. The Messages application gives some control, showing multiple account names and protocols when composing a new message. Message senders need more control over where and how they intend their messages to appear. On the other hand, this may just be a short-term cultural problem caused by the strange financial and technological conditions that gave birth to SMS.īut if all text-based messaging protocols are to be combined into a single application, then more clarity and control is needed. There's a strong argument to be made that what we've come to know as "instant messaging" and "texting" are sufficiently different in terms of the expectations of both the sender and the recipient that separate applications are warranted.
Oops, did you just mean to send a message to your colleague down the hall as he sat at his Mac? Or did you mean to send a text to someone's phone and not cause an alert to appear on his iPad which is currently being used by his child to play a game? Send a message using the Messages application and a window may appear on one or more Mac screens, a notification dialog (and sound) may appear on iPads or iPod touches, and someone's phone may vibrate in their pocket. The new interface combined with the new protocol leads to an experience that I found confusing. But the big selling point of Messages is its support for Apple's iMessage protocol, a replacement for SMS/ MMS that doesn't rely on cell carrier networks (and their text message payment plans) to operate. Unlike Messages in iOS, the Mac version retains iChat's multi-protocol capabilities, with support for multiple AIM, Jabber, Google Talk, and Yahoo instant message accounts. The prominence of the search feature is a big change from iChat, which relied on Spotlight to find old chats. The search box filters the list as you type, showing only the conversations that match the text that's been entered. Double-clicking a conversation opens it in a separate window. This helps separate old conversations from new ones, but it also means that the click targets in the sidebar are constantly moving. When text is added to a conversation, it jumps to the top of the list. Confusion replaces familiarity.Īs on iOS, the sidebar holds a list of all conversations, past and present, until they're explicitly deleted.
0 kommentar(er)
