Open Thread: To Hack or Not to Hack, That is the Question

Seems you can’t shake a stick without running into an article about Apple vs. Users (and 3rd party Developers) over the iPhone. Apple has said all along that it’s their way or else. Now the “or else” comes in the form of a firmware update that not only takes away 3rd party unauthorized applications that customers have installed on their iPhones, but also “bricks” phones that have been unlocked so users can make calls with a provider other than AT&T.

It’s an arms race…with Apple throwing up road block after road block to keep their wonder-device closed, and developers finding workaround after workaround. Apple responds, developers respond…everyday users who aren’t hacking their iPhones are caught in the middle.

On the one hand, Apple has the right to dictate the technology that is on their devices if folks want Apple to continue to support and update said device. You never know what kind of trouble those hacks can cause later on down the line. Not to mention that there’s a very lucrative relationship with AT&T to protect. On the other hand, folks want to get the most out of the technology they’ve purchased. 3rd party applications and multi-carrier support have been a hallmark of mobile hardware for a long time. This isn’t the kind of “Think Different” folks have been looking for from Apple.

What’s your take? Is Apple being unreasonable? Are the users threatening lawsuits out of their mind?

Going beyond the iPhone, do you use your technology as the manufacturer dictates right out of the box, or do you push the barrier? If you tweak, how far do you take it and what is your expectation of the reaction you should get from the company if you do?

loading

Comments have been disabled for this post