I don't particularly like defending any DRM system, but Adobe's is not as bad as you make it out to be. Although this isn't documented anywhere, I remember once reading a forum post from an Adobe employee who explained that they automatically add additional device authorisations over time to account for device lifecycles. If you do reach the limit, Adobe customer service will reset it on request. I can corroborate this from personal experience.
Also: ADEPT has been comprehensively broken. Stripping the DRM from ADEPT files is trivial with readily-available Python scripts.
Slashdot Mirror
I don't particularly like defending any DRM system, but Adobe's is not as bad as you make it out to be. Although this isn't documented anywhere, I remember once reading a forum post from an Adobe employee who explained that they automatically add additional device authorisations over time to account for device lifecycles. If you do reach the limit, Adobe customer service will reset it on request. I can corroborate this from personal experience. Also: ADEPT has been comprehensively broken. Stripping the DRM from ADEPT files is trivial with readily-available Python scripts.