“...Silverlight snubs GNU/Linux and it will never be ported to that platform. ”Using Novell's helps (with Mono and Moonlight), Microsoft is still hoping to tighten its grip on the Web and be able to exclude rivals at will. Already, as a matter of fact and principle, Silverlight snubs GNU/Linux and it will never be ported to that platform. Microsoft is targeting -- in a malicious sense of course -- both Flash and PDF format (from Adobe/old-age Macromedia) at the same time. It also hopes to introduce Windows DRM as part of its offerings, too. Recall what was said last week about this fight against Adobe and Free software as the motor of the Web.
We have recently given several examples of practical ways in which Microsoft forces people to use Silverlight, or at least 'punishes' those who cannot use it (hello, Linux users). Consider the Olympic games and some video sites (mind the mentioning of Yahoo also). Given Novell's existing 'advertisements' of Windows Vista, it would be almost predictable for them to put some Silverlight in Novell.com sooner or later ("buy SLED or Novell 'protection' for Moonlight to view this site almost properly").
Here is another new report that combines and revisits several elements or patterns we have come across before: acquisitions, Silverlight, software patents.
LiveStation, which Microsoft Research co-developed with Skinkers, includes a client-based player that runs on top of Silverlight, Microsoft’s rich-media technology.
[...]
Microsoft acquired a minority equity stake in Skinkers in exchange for Skinkers’ use of the Microsoft P2P intellectual property.
Now Adobe, which controls Flash and Flash Video, is trying to change that with the introduction of DRM restrictions in version 9 of its Flash Player and version 3 of its Flash Media Server software. Instead of an ordinary web download, these programs can use a proprietary, secret Adobe protocol to talk to each other, encrypting the communication and locking out non-Adobe software players and video tools. We imagine that Adobe has no illusions that this will stop copyright infringement -- any more than dozens of other DRM systems have done so -- but the introduction of encryption does give Adobe and its customers a powerful new legal weapon against competitors and ordinary users through the Digital Millennium Copyright Act (DMCA).
“Remember that Novell's support for OOXML is done using Mono and remember that OOXML embeds DRM capabilities too.”It's not just media companies that love DRM, mainly because DRM makes media application- or platform-specific, augmenting the existing problem of application and data compatibility to form a new class of lock-ins. Simplified example: think along the lines of "your song is only compatible with Microsoft Windows Vista and expires in 2009."
The role of Flash (and Silverlight) is ever more evident when it comes to video. These can be used to build applications as well, but there won't be many takers for a whole bunch of reasons. With videos and binary implementation comes DRM, which brings back to mind the recent discussion about Mono as a "ramp" for WMV, DRM, and the likes of that. It might just be an implementation bridge, a programmers' hook. That, among other reasons, is why Mono worries us. Remember that Novell's support for OOXML is done using Mono and remember that OOXML embeds DRM capabilities too.
The Inquirer is not a publication to be taken too seriously (nor lightly) when it's sarcastic, but Charlie Demerjian, a faithful Linux user, has this bizarre new 'interview' with Miguel de Icaza:
Inq: Why did you name your biggest project after an infectious disease?
Miguel: Because I am Mexican and in Spanish, Mono means monkey.
Inq: Thank you for your time.
Comments
jo Shields
2008-12-13 18:09:05
Roy Schestowitz
2008-12-13 19:53:14
http://www.nabble.com/Re%3A-OdfConverter-p15020575.html
"Novell builds odf-converter using Mono, and distributes it as a so-called bundled executable (platform-specific executable that includes the Mono runtime, i.e. not a platform-independent managed .NET executable) for Linux and Windows."
jo Shields
2008-12-13 20:12:09
By "Novell’s support for OOXML" what you actually mean is "Novell’s support for ODF". No, wait, sorry. The REALITY is "Novell’s support for ODF", you definitely MEANT to lie
Roy Schestowitz
2008-12-13 20:23:14
How the goalposts have moved.
You totally changed the subject after being proven wrong. Can I please have my apology?
jo Shields
2008-12-13 20:33:23
You're asserting that adding ODF support to MSOffice is "OOXML support"?
Roy Schestowitz
2008-12-13 20:36:56
jo Shields
2008-12-13 20:41:31
Roy Schestowitz
2008-12-13 20:50:09
jo Shields
2008-12-13 20:54:07
You're seriously claiming that writing a library in a language counts as an insidious black mark?
I heard people write trojans and rootkits in C. Obviously GCC's support for rootkits should be investigated.
You really do make yourself out to be a complete fruitcake sometimes, Roy
Roy Schestowitz
2008-12-13 20:57:10
jo Shields
2008-12-13 21:06:46
The odf-converter, an obsolete plugin to allow Windows users to work with ODF rather than OOXML, uses bundled Mono - meaning it's essentially no different from a user perspective to a C-based app. Using Mono is a programmer convenience. It doesn't "spread" Mono any more than a static app "spreading" libc6. But I know how much you hate reality.
And more to the point, do you even know whether this "OOXML SDK" *works* on Mono? It may well be full of Windows-only P/Invokes. Making it useless to non-Windows platforms and Mono users alike.