Quote:
Originally Posted by pdurrant
It's occurred to me that Adobe has gone about this in entirely the wrong way. The linking of CS5 with RMSDK10 is ridiculous and unnecessary.
If they wanted to do this damn fool thing (new DRM system), they shouldn't have done it in this damn fool way.
What they should have done was roll out RMSDK10 first. It's a nice update - new features, including better ePub support. They should then have encouraged manufacturers to produce updates to the firmware of existing devices, and required it for approval for new devices. And then, next year sometime, rolled out CS5 and enforced the new DRM. Most users would have already updated, with only a small minority left with orphaned devices still using RMSDK9.
In fact, I can't really see why they didn't do it this way.
|
I can see two reasons:
The most likely is that this is how they roll. They dictate and customers comply. That is how they handled the pdf DRM switch a few years back, that is how they forced customers to the Suite subscriptions. (
http://news.cnet.com/8301-1001_3-575...subscriptions/)
The other reason is they might think they can't wait another year. The drumbeat for DRM-free is getting too loud. (There is the Tor experiment proving encryption-DRM doesn't reduce piracy in any meaningful way. There is the horde of indie publishers prospering through DRM-free sales. There is the clamor of pundits telling publishers that DRM helps demon Amazon. There is the increasing awareness of the Adobe tax. And there is the alternative of watermark-DRM.) They may be thinking they need to go to hardened DRM now before their customers give up on encryption DRM altogether.