undefined | Better HN

0 pointsPxtl12y ago0 comments

If it's just going to end-up plug-ins, I don't understand why DRM is being treated specifically at all instead of tweaks to the existing general-purpose plug-in architecture. If you want DRM, deal with Microsoft Silverlight or Adobe Flash or roll your own.

0 comments

akjj12y ago

The existing plugins are heavy and don't integrate well with other web technologies. In addition, the NPAPI interface is not standardized (I believe). Thus, the point is to narrow down the scope of plugins from everything that Flash and Silverlight do to just a piece of code focused on DRM. Everything else that people use Flash and Silverlight can be replaced by standards and directly implemented in the browser. However, DRM, by its nature depends on closed-source compiled binaries, which means that it has to remain in a plug-in.

mikeryan12y ago

You can, of course folks have, but then you can't use the video/audio tags. (or you need a pretty significant js shim)

chinpokomon12y ago

But this still effectively limits the rendering of content to blessed implementations. Why introduce a standard that isn't open when there are already other options.

j / k navigate · click thread line to collapse