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 don't think it really matters. The vast majority of the user's aren't going to make the decision on upgrading the device firmware or their ADE version based on the new DRM. The issue remains that when the new DRM gets enforced it is going to break for some end users. If they do it later it impacts less users.
I suspect that it's a hot potato situation. Adobe has probably been getting heat because the existing DRM is so easy to break. They've come out with a solution to address the concern. They've proposed a timeline to implement it
and now they've been told that's too soon. Now they can toss the hot potato back and say it's not Adobe's problem.
Maybe what I should have said is "Here's the gun, it's loaded and pointed at your foot. You decide when to pull the trigger."
