Linked by Thom Holwerda on Sun 19th Jun 2011 18:26 UTC
Windows Way back in old and boring January of this year, Microsoft announced they would be working together with the Windows Phone 7 homebrew community, with the goal of creating a stable, supported way for homebrew developers and people interested in homebrew applications to enable side-loading on their WP7 devices. Well, they took their sweet time, but the ChevronWP7 team (Rafael Rivera, Chris Walsh, and Long Zheng) and Microsoft have just announced the results.
Permalink for comment 478407
To read all comments associated with this story, please click here.
RE[7]: LOL
by tomcat on Thu 23rd Jun 2011 23:39 UTC in reply to "RE[6]: LOL"
tomcat
Member since:
2006-01-06

1/You'll need a documented and tested low-level interface for device manufacturers to code drivers anyway.


No, it's completely different. You're talking about a very small set of driver DDIs for a limited set of devices; whereas, opening the engineering specs exposes the device to a potentially unlimited set of partners. That will increase your costs.

2/People pay quite a lot of money for their phone, either directly or through their phone plan (with a nice premium in the latter case). Shouldn't part of that money cover the engineering costs of the operating system ?


No. You buy an expensive car, you don't get schematics for the components in that car, either. You don't get schematics for your DVR or your Blu-Ray player or virtually other kind of consumer device.

3/If the hombrew interface is sufficiently obscure, you don't lose control on the app market. Jailbreaking exists, yet I don't think there's anyone here ready to argue that Apple keeps a tight grip on everything related to iOS.


The reason that hacking isn't more common is that manufacturers will void your warranty if you're running a jailbreak device. And I don't blame them. Who would want to support a broken device that's the result of hacking?

Reply Parent Score: 2