Earlier quoted context omitted.
As someone who works in the ebook sector, I'll say that no one loves Adobe's DRM, whether it be the publisher, vendor or user. It's implemented by apps and such because of the network effect - other apps support it, and users want to be able to read Adobe DRMed content without trouble, and it was also the first big solution to the "problem" of ebook DRM. However, because people have to pay a fee to Adobe per license,…
Hadn't heard of LCP before. Based on some skimming of the website… how does it improve on Adobe's DRM other than cost? It's still limited to applications that explicitly support it. Maybe there will be a wider ecosystem than Adobe's. But my current preferred reader apps all either have built-in storefronts (Kindle, Apple Books) or are open source (Calibre and Google Chrome, so I can use a Japanese dictionary extensio…
As for LCP being around in 10-20 yrs, the idea with LCP (excluding loans, of course) is that you don't need to be online or require a remote server to validate/access ebooks you've downloaded. You just have your "password", that is used to decrypt the book content through LCP, so as long as you still have any app that supports LCP, you still have access to the publication. I think it's the best compromise that will exist in reality for publishers that still want DRM. The entire system is open-source except a small key derivation function.