4 ms·

I don't think I phrased that quite right. Modern web standards are attempting to render plugins like java, flash, and silverlight obsolete, because they're fra

by bcoates 13y ago

I don't think I phrased that quite right. Modern web standards are attempting to render plugins like java, flash, and silverlight obsolete, because they're fragile, not universally available, single-sourced, proprietary, insecure and generally inconsistent with how the rest of the web works. There is an effort from various direction to kill off content viewer plugins like them, and the APIs that allow them to exist, and it appears it's going to succeed. You're right that EME is meaningless one way or another so long as plugins exist--That's why EME exists at all, it's essentially a new plugin architecture that solves none of the problems of the previous ones. It's a bad idea for the same reason plugins are.

cleverjake 13y ago
I still don't really understand what you are trying to say >> There is an effort from various direction to kill off content viewer plugins like them, and the APIs that allow them to exist, and it appears it's going to succeed. While I agree that there are people trying to kill off the need for plugins, I don't think anyone is killing off the APIs that allow for plugins - can you provide any example of this happening? (Outside of phones) >>You're right that EME is meaningless one way or another so long as plugins exist I never said that. Nor do I think that. My point is that EME is doing the same thing as other - long ago implemented - plugins, but with a lot less of a surface area of attack and more likely to be made up of better code. >> it's essentially a new plugin architecture agreed. >>that solves none of the problems of the previous ones. I don't believe that most people would list DRM-ablility as an issue with previous plugins. Could you elaborate what issues you are referring to? >>It's a bad idea for the same reason plugins are. I think that those plugins are bad because it gives flash/silverlight/java/anythingElse access to a lot of native APIs that most users are completely oblivious to. If anything, it removes most of the security issues shown in those plugin systems.

by bcoates 13y ago

cleverjake 13y ago

I still don't really understand what you are trying to say >> There is an effort from various direction to kill off content viewer plugins like them, and the APIs that allow them to exist, and it appears it's going to succeed. While I agree that there are people trying to kill off the need for plugins, I don't think anyone is killing off the APIs that allow for plugins - can you provide any example of this happening? (Outside of phones) >>You're right that EME is meaningless one way or another so long as plugins exist I never said that. Nor do I think that. My point is that EME is doing the same thing as other - long ago implemented - plugins, but with a lot less of a surface area of attack and more likely to be made up of better code. >> it's essentially a new plugin architecture agreed. >>that solves none of the problems of the previous ones. I don't believe that most people would list DRM-ablility as an issue with previous plugins. Could you elaborate what issues you are referring to? >>It's a bad idea for the same reason plugins are. I think that those plugins are bad because it gives flash/silverlight/java/anythingElse access to a lot of native APIs that most users are completely oblivious to. If anything, it removes most of the security issues shown in those plugin systems.