Linked by Thom Holwerda on Mon 9th Apr 2012 12:02 UTC
Permalink for comment 513392
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2011-01-28
grantpalin,
"The possible upside of this move is that app developers may feel better about developing for the Playbook with piracy out of the picture. On the other hand, if developers simply weren't interested before, the perspective may not change after."
You're comment covered two possibilities but ignored another: some developers are put off by monopolized app distribution channels. I thought the possibility should be mentioned since it covers most open source guys and some proprietary ones who'd rather market and distribute themselves.
Anyways, I personally feel DRM is mostly evil and hurts legitimate users more than anyone else by curtailing fair use rights, etc. Never the less, as misguided as I find DRM to be on both technical and moral fronts, I do understand the motivation of executives to buy into it. However if RIM's intention was just to offer better copy protection, it should just offer it's DRM API's to all developers regardless of sideloading.
Edit: I'm assuming RIM has DRM at all, but I suppose it might not have any DRM to offer developers? I don't know, but time and time again the solution is to improve sandboxing rather than to disable sideloading.
Edited 2012-04-09 22:26 UTC