Last night, the ChevronWP7 team posted a new blog on their upcoming meeting with Microsoft in Redmond next week. At that discussion, they plan to put forth the argument as to why the Hombrew community is important as well as the general feeling on improving the OS:
We’ll be sharing our perspective on the homebrew potentials of Windows Phone 7 and some of the wider community feedback around the platform. In addition to our homebrew focus, we will also be pushing for stronger protection of WP7 developer intellectual property (IP) on the platform as we believe both can co-exist on the platform.
Sounds pretty good. But then again, there's certainly no commitment from Microsoft to embrace or work towards a hombrew community. It seems that you can only have it all open or all closed, but in between is hard to navigate. But hey, there's some smart people around discussing this stuff so maybe a workaround can be reached?
The second big bombshell is that ChevronWP7, technically discontinued, will no longer work after the upcoming 'NoDo' update:
Although this has been subtly communicated before, we’d like to reiterate Microsoft has informed us the “coding error” used in the ChevronWP7 unlocker will no longer work after the next Windows Phone 7 update (officially announced at CES 2011).
So that's that, evidently. Of course we imagine some other young, starry eyed team will come a long and we'll repeat the whole process by say....March or April. Much like the locked-unlocked-locked cycle of the iPhone and the Cydia community, this has the potential to go on for a long time. However, if Microsoft comes up with a Homebrew solution, that would easily nip in the bud the desire for more black-hat activities amongst the community.
Maybe we're cynical, but we're just not holding our breath on the homebrew thing happening. Your thoughts?
Source: ChevronWP7; via @ChrisWalshie
