I don’t think I would start using .NET because of this, but wow, what a step in the right direction for Microsoft!
I got a new phone over the summer, and it took me a while to realize that it couldn’t receive some text messages. It seemed to randomly fail; sometimes it would work, sometimes it wouldn’t. Eventually I found out that iPhone users couldn’t text me if they had texted me before. The problem was that I no longer had an iPhone; I had switched to Android. Apple’s iMessage was intercepting my texts because I didn’t know to turn off iMessage on my old phone before wiping and selling it. That was an unexpected pain when switching from an iPhone to a competitor’s phone.
I found an Apple knowledgebase article about the issue, which instructed me to call Apple support. To my surprise, the only option for support was to pay a pretty hefty service fee — which was thankfully waived after I explained the iMessage bug. Apple explained that it was a known issue, and they then instructed me to contact everyone I knew who had texted me from their iPhone to tell them to delete all the threads that I had been a part of. (I almost fell out of my chair when I heard that.) They also said that my contacts could also turn off iMessage entirely to avoid the problem for me and any other contacts that might switch from an iPhone (e.g. my wife) — which I recommended to everyone I talked to.
Those were incredibly awkward conversations to have, particularly because several iPhone users seemed to think that I was contacting them because of a text messaging bug in Android. (Keep in mind that most non-technical users don’t know the difference between an iMessage text message and an SMS text message.) I’m sure that a few still think that Android is buggy and are now afraid to switch away from Apple products in fear that they won’t receive any text messages. It’s not hard to think of a few reasons that Apple would take years to fix this problem.
To be clear, iMessage was a problem for me even when I used an iPhone daily. The service has had a surprising number of issues that have prevented users from receiving messages, though most of those were fixed in a relatively-timely manner. For example, I had serveral problems with multi-person threads. Ironically, I wouldn’t receive any messages from the other iPhone users on the thread, but the Android users would get messages just fine. The iMessages went into oblivion, and I would just get a confusing half of a conversation from the Android user who was obviously responding to something that had been said. That happened multiple times over a period of months; it wasn’t just a couple of forgivable, short service disruptions.
It’s still my recommendation to turn iMessage off, especially if you have free text messages as a part of your phone service. All it takes is a trip to “Settings.”
From my posts on the Meetup event:
It’s almost the first Thursday of the month again. We’re always interested in having members present Ruby-related topics to the group, so if you’ve been playing with anything cool, please consider presenting! We’re pretty informal, so anything you present doesn’t have to be a “polished” keynote-style presentation; it can be as simple as plugging in your laptop and showing some code you’ve been working on.
If anyone would like to present something, please leave a comment [on the Meetup event].
And also, my customary monthly Ruby news roundup:
Some Ruby news from the last month:
- Ruby 2.1.4 released, along with patchlevel-releases for 2.0.0 and 1.9.3 containing security fixes
- OSX 10.10 has shipped, with Ruby 2.0.0 as the default (Ruby 1.8.7 was completely removed)
- Rails 3.2.20, 4.0.11, 4.1.7 released (security fixes) on Oct 30th
- Last Rails 4.2.0 beta released, release candidates coming soon.
- Ruboto 1.2.0 released, with support for ART on Android Lollipop (5.0)
- Raptor — new Ruby web server — coming out this month. Supposed to be high performance.
Not the behavior I expected; makes me wonder what documents I have stored in iCloud without my knowledge. Either way, I’m happy Apple is moving to a more Dropbox-like strategy.