But if the DRM solution is implemented through JS code in the browser, it is trivial to pirate. I know DRM is always broken, etc., but at the same time it is hard to take an argument at face value that discounts the security differences between these approaches.
JS is trivial for anyone moderately skilled to crack - you're sending content in the clear from the browser through the stack.
DRM solutions enabled by EME can be much more robust and difficult to crack.
Similar to other commentators, I struggle with the issue, but just saying "put it in JS" is not a very compelling argument. The current EME approach of a publically defined API that any DRM solution can plug into feels like a pretty reasonable compromise here.
JS is trivial for anyone moderately skilled to crack - you're sending content in the clear from the browser through the stack.
DRM solutions enabled by EME can be much more robust and difficult to crack.
Similar to other commentators, I struggle with the issue, but just saying "put it in JS" is not a very compelling argument. The current EME approach of a publically defined API that any DRM solution can plug into feels like a pretty reasonable compromise here.