Slashdot Mirror
GNOME Foundation Helping OOXML?
christian.einfeldt writes "According to long-time OpenDocument Fellowship member Russell Ossendryver, it appears that GNOME founder Miguel de Icaza's widely-publicized praise for OOXML as a 'superb standard' is being followed up with on-going support by the GNOME Foundation in 'resolving' the thousands of criticisms leveled against Microsoft's proposed standard. In an open letter in his blog, Ossendryver urges the GNOME Foundation to halt its apparent support for OOXML as a standard and to put its efforts behind enhancing adoption of the genuinely open standard, ODF, which was approved by the world standards bodies as ISO/IEC standard 26300 on 2 May 2006."
I was just about to say something closely approximating that.
What annoyed me most before this (which is simply unthinkable) was his extremely strong support of Mono. Personally, I feel that Mono, like Wine, should be treated as a compatibility layer to run software intended for other operating systems, not a viable target for open-source application developers. If everyone likes C# so much, then we should take matters into our own hands and implement a language with the features we like that is under our control! (My concern with Mono following Microsoft's language is that in the event that Microsoft changes a significant feature, like Java did when it added assert, Mono would almost certainly make the same change, leaving a bunch of open-source developers to deal with the whims of Microsoft.)
At some point, until Microsoft starts releasing truly open-source code and letting everyone hack on Windows, we have to keep at least some distance from Microsoft. There's nothing wrong with attempting to run their software, but we shouldn't be writing Windows software just because it's more convenient and we now have a way to run it on Linux.
ttuttle is a rankmaniac
>What better way to lure Windows users away than to provide support for the formats their existing documents are probably already in?
.doc
Which is fine - if you had any chance of competing. But as you said - large sections are binary. With that in place, you're not much better of than parsing a
Peter.
The article author is either stupid beyond belief or deliberately trying to cause spite and malice. Neither GNOME the project, nor The GNOME Foundation is in any way or form backing OOXML! Miguel de Icaza is, but most other foundation members are staunchly against it. Not that it matters, there is a big fucking difference between individuals opinions and the stance of an organization. If the author has some beef with de Icaza, then he should say so, but don't try to paint the GNOME Foundation with the same brush. Fucking moron troll.
Football Odds
The vast majority of Windows users do not have any documents in the OOXML format. The handful of people I know who use newer versions of office are pissed off everytime they forget to "save as" into an older format and that is because of where I work. All work computers are setup with an older version of office (can't remember the version number off the top of my head). These people usually end up switching to an older version of office and I have been able to con some of them into using openoffice.org. A handful have been happy with oo.org, but most just wanted the same version of office as they have at work.
I agree that binary compatibility should be strived for, but it is not ooxml that needs compatability. its the older binary office formats that need to be standardized against. What needs to be done about ooxml is a concerted effort to prevent adoption. This means pushing organizations to switch away from newer versions of office. This also means helping oo.org or your fav alternate office suite getting competitive (assuming u have any means to help).
at my work, people use powerpoint and recently access (my fault - i needed something that was there and people could use). oo presentation is good enough (import and export from powerpoint), but database capabilities are severely lacking.
When all else fails, try.
But I wouldn't be surprised. Mr. Miguel de Icaza has been very clear about his love for Microsoft and "their" technologies. I never actually hear him choosing community technologies to boast, but maybe that is just due to bias reporting. Either way, it will be interesting to see his reaction if think ever really go bad. I'd also be interested in hearing his opinion on the recent law suit against RedHat.
"Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
Miguel has stated why he likes OOXML: it's easy to take an existing Microsoft Word reader/writer and turn it into an OOXML reader/writer, because the file structures are so similar. That makes transitioning existing Microsoft-compatible software to OOXML much easier than transitioning to ODF.
That's a reasonable position. I still think it's wrong.
The purpose of an XML document format is to enable other people to do interesting things with the format, not to make life easy for the few people porting existing Microsoft Word compatible software. Furthermore, open source projects need to support ODF anyway because ODF is here and it's here to stay.
For all I know, they offered him a better job outside Microsoft for a nice thirty pieces of silver collectible at some future date. Every time I read his name, it's in connection with something I see as damaging to Linux and the Free Software movement. And surely nobody can describe OOXML in these terms without some sort of bias?
Gnome is GPL, isn't it? Doesn't that make it inherently possible for people to sideline this person no matter his current position, before we risk serious damage? In terms of patents, introduction of copyrighted code, or perhaps other issues, presumably someone in his position acting deliberately, could cause some nasty legal wrangles. And actions so far give reason for distrust, do they not?
Aide-toi, le Ciel t'aidera - Jeanne D'Arc.
I dislike Gnome more by the day. While I know and fully agree with the idea that you can't make an unpaid programmer work on something he doesn't want to work on, I can't help but wonder where KDE would be if Gnome wasn't siphoning off potential developers. Since it's generally accepted that at least one of Gnome's core developers (Miguel) is a Microsoft patsy, and that FOSS market fragmentation is very convenient for Microsoft, the professional paranoid in me can't help but to see connections even if there aren't any.
Gnome devs: ditch Miguel. I'm not the only person that's starting to look at you guys suspiciously. Guilt by association, you understand.
Dewey, what part of this looks like authorities should be involved?
He always gets sidelined. He mostly starts something or writes it badly but with some key interesting kernel. The "badly" is usually trying to mimic some underdesigned overengineered buzzword from MS - he seems to be enamoured by their financial success and thinks it is the intrinsic value of their technology that did it. Of course, it isn't - their success is due to acute business acumen and marketing ability.
GNOME (the GNU Network Object Model Environment) was designed around a COM approach (it actually used that well-known failure and DCOM copycat, Corba). Microsoft is abandoning COM, and using it (usually because the financial director told them that it will save money and is better anyway) costs developers a vast amount of time, money, and reputation as the interface conventions are appallingly unstructured. Suffice it to say, GNOME is moving away from corba and has been for some time.
Generally, it is a good idea to watch for what problem Miguel de Icaza wants to solve and then start solving the problem differently before he can damage Linux' reputation for several years until his plans are ripped out and replaced as they usually are.
What surprises me the most is that this actually has to be said. It is ridiculous that mono is so actively used to actually make programs for official gnome, we got python, we got Java, we got Ruby, we certainly did not need MONO here.
I can foresee somebody telling me it is about picking the best tool for the job. But then HOW IN EARTH would MONO be the best tool for this job? The intention is to make open source free software, and adding any unnecessary dependance on MS technology is ridiculous, and it is really making gnome look bad, I actually hope KDE4 lives to the expectations so I can move. Really.
Copyright infringement is "piracy" in the same way DRM is "consumer rape"