1,893 karma · joined June 30, 2010
DRM can't be implemented in a simple binary plugin since the user will still be able to copy the protected content by e.g. modifying the video driver. All system layers from EME module in a browser to hardware will need to be restricted from modification. Do you believe that Secure Boot was created just for malware protection?
DRM-enabled Firefox would be effectively non-free software: you could not modify it and rebuild it from source while retaining the DRM functionality.
What I learned from my own experience with GNOME 3 (I really like it) and from observing other people's reactions, is that we tend to overestimate the importance of our old habits and are willing to put more effort to protect them than it would take to change them (e.g. spending all day figuring out how to customize the UI while it would take an hour to get used to the defaults).
And we also need distributed search engines (https://en.wikipedia.org/wiki/Distributed_search_engine).
JVM and CLR are not very different. What would be the reasons to want to avoid JVM, but still consider CLR as an acceptable choice?
And then if the government say that they stopped, how can you ever be sure they did?
Unless we use free (as in freedom) software, open encrypted communication protocols, and decentralized network services, we are trusting too much of our computing and communication to third parties, which are subject to political powers, that always do whatever they can to protect themselves. The government should not be trusted, it must be controlled. Corporations should not be trusted either.
DRM always implies restricting user control over their own computers.
Here is an overview of performance techniques used by the Java HotSpot VM: https://wikis.oracle.com/display/HotSpotInternals/Performanc...