MS Palladium Technical Talk at Harvard
An anonymous reader writes: "On December 4, John DeTreville from Microsoft Research will give a technical presentation about Palladium, Microsoft's Digital Rights Management effort. The talk is open to the public and is a good chance to ask questions."
I went to Harvard, simultaneously my best friend to MIT; they are very different places. How will this talk differ from the MIT presentation previously discussed? (Predictions, stated agenda, etc.)
:)
(And has Microsoft recovered from the MIT presentation yet?
...If I weren't hundreds of miles from Harvard.
1. How does Microsoft plan to allow non-proprietary Operating Systems access to Paladium media?
(Assuming "we don't" is the first answer:)
2. Why would consumers want to purchase your product that removes rights they have over their own media?
(Correct answer: We're a monopoly and they have no choice in the matter. We're serving our own market interests and not those of our customers. We're using our desktop monopoly to gain a stranglehold on all digital media as well, just as we're not supposed to under antitrust law.)
How does encrypting a user's files with a key, and then denying the key to the user improve security ?
The user can no longer independently access his own files, thereby considerably DECREASING security, most defineately not increasing.
Ask him if Palladium will provide a way to support DRM for new media types like DVD Audio or some kind of future enhancement of DVD.
and try to make a recoding of the event.
Does anyone have any questions they'd like to have asked?
III.IIVIVIXIIVIVIIIVVIIIIXVIIIXIIIIIIIIVIIIIVVIII
Let's have a close look at the costs involved when running a Linux system.
An important factor in Linux' cost is its maintenance. Linux requires a *lot* of maintenance, work doable only by the relatively few high-paid Linux administrators that put themselves - of course willingly - through an expensive and time consuming certification process. Linux seems to be needing maintenance continuously, to keep it from breaking down.
Add to this the cost of loss of data. Linux' native file system, EXT2FS, is known to lose data like a firehose spouts water when the file system isn't unmounted properly. Other unix file systems are much more tolerant towards unexpected crashes. An example is the FreeBSD file system, which with soft updates enabled, performance-wise blows EXT2FS out of the water, and doesn't have the negative drawback of extreme data loss in case of a system breakdown.
According to Linux advocates, an alternative to EXT2FS would be ReiserFS. Unfortunately, ReiserFS is still in beta stage. This means it is not intended for production use (although according to many Linux advocates this shouldn't be a problem, which makes me wonder how (little) valuable they find your data).
The other proposed 'solution', EXT3FS, is nothing more than an ugly hack to put journaling into the file system. All the drawbacks of the ancient EXT2FS file system remain in EXT3FS, for the sake of 'forward- and backward
compatibility'. This is interesting, considering that the DOS heritage in the Windows 9x/ME series was considered a very bad thing by the Linux community, even though it provided what could be called one of the best examples of compatibility, ever. When it's about Linux, compatibility constraints don't seem to be that much of a problem for Linux advocates.
Back to Linux' cost. Factor in also the fact that crashes happen much more often on Linux than on other unices. On other unices, crashes usually are caused by external sources like power outages. Crashes in Linux are a regular thing, and nobody seems to know what causes them, internally. Linux advocates try to hide this fact by denying crashes ever happen. Instead, they have frequent "hardware problems".
The steep learning curve compared to about any other operating system out there is a major factor in Linux' cost. The system is a mix of features from all kinds of unices, but not one of them is implemented right. A Linux user has to live with badly coded tools which have low performance, mangle data seemingly at random and are not in line with their specification. On top of that a lot of them spit out the most childish and unprofessional messages, indicating that they were created by 14-year olds with too much time, no talent and a bad attitude.
I could go on and on and on, but the conclusion is clear. Linux is not an option for any one who seeks a professional OS with high performance, scalability, stability, adherence to standards, etc.