Whatever the cause, the timing is obviously terrible: Plenty of people surely received one of the two consoles as Christmas presents today, while many more gamers would have happily spent the afternoon in front of the TV. In the meantime, both Sony and Microsoft have acknowledged the problem, with Sony issuing a tweet and Microsoft posting a message on its support website: "We're working to address this as quickly as we possibly can," reads its status website. "Thanks for your patience, Xbox members." In an email, a Microsoft spokesperson declined to comment further or say when the company expects to restore service. We've also asked Sony to comment and will update this post if and when it does. The Xbox Live status page says service remains "limited," and the Playstation Network is listed as offline.
In 2012, Vonage reported its year-over-year voicemail volumes dropped 8%. More revealing, the number of people bothering to retrieve those messages plummeted 14%. More and more personal and corporate voicemail boxes now warn callers that their messages are rarely retrieved and that they're better off sending emails or texts. "The truly productive have effectively abandoned voicemail, preferring to visually track who's called them on their mobiles," concludes Schrage. "A communications medium that was once essential has become as clunky and irrelevant as Microsoft DOS and carbon paper."
1. whether this means Microsoft is no longer the enemy of the open source movement
2. if not, then does it mean Microsoft has so lost in the web server arena that it's resorting to desperate moves.
3. or nah — it's standard Microsoft operating procedure. Embrace, extend, extinguish.
What I'd like to ask is whether anybody that's not currently a .NET fan actually wants to use it? Open source or not. What is the competition? Java? PHP? Ruby? Node.js? All of the above? Anything but Microsoft? Because as an OSS advocate, I see only one serious reason to even consider using it — standardization. Any of those competing platforms could be as good or better, but the problem is: how to get a job in this industry when there are so many massively complex platforms out there. I'm still coding in C, and at 62, will probably live out my working days doing that. But I can still remember when learning a new programming language was no big deal. Even C required learning a fairly large library to make it useful, but it's nothing compared to what's out there today. And worse, jobs (and technologies) don't last like they used to. Odds are, in a few years, you'll be starting over in yet another job where they use something else.
Employers love standardization. Choosing a standard means you can't be blamed for your choice. Choosing a standard means you can recruit young, cheap developers and actually get some output from them before they move on. Or you can outsource with some hope of success (because that's what outsourcing firms do — recruit young, cheap devs and rotate them around). To me, those are red flags — not pluses at all. But they're undeniable pluses to greedy employers. Of course, there's much more to being an effective developer than knowing the platform so you can be easily slotted in to a project. But try telling that to the private equity guys running too much of the show these days.
So, assuming Microsoft is sincere about this open source move,
1. Is .NET up to the job?
2. Is there an open source choice today that's popular enough to be considered the standard that employers would like?
3. If the answer to 1 is yes and 2 is no, make the argument for avoiding .NET.