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."

32 of 471 comments (clear)

  1. No surprise here... by Azuma+Hazuki · · Score: 4, Insightful

    Miguel de fucking Icaza has been kissing Microsoft's ass for years now. Can we please get rid of him already?!

    --
    ~Eien no Inori wo Sasagete~ Searching for my Hatsumi...
    1. Re:No surprise here... by ThinkingInBinary · · Score: 5, Interesting

      Miguel de fucking Icaza has been kissing Microsoft's ass for years now. Can we please get rid of him already?!

      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.

    2. Re:No surprise here... by rbanffy · · Score: 4, Insightful

      Right...

      It will work wonders when all the five users of the two programs that actually use what Mono has that .NET hasn't start raving and evangelizing people into running Mono on free platforms.

      You must have market dominance to play Embrace and Extend. Otherwise, you will follow all those neat enhanced supersets of whatever technology was mainstream at the time into oblivion.

    3. Re:No surprise here... by segedunum · · Score: 4, Insightful

      One cool thing about mono is that they're using MS' strategy right back at em: Embrace and Extend. In some ways, Mono has more features than .NET, and in some cases (Silverlight 1.1) is ahead of Microsoft.
      The problem is, they're not embracing and extending anything because they're not doing so from a position of any kind of power or authority. Microsoft's version is the reference version of .Net, owing to the fact that it is what is installed on Windows machines and the installed based of Windows. If it works on Mono then it's a bonus, and if it doesn't work on Mono then it's tough luck. End of story. Being a sheep is never a good idea. Sheep get slaughtered.

      That should make quite a few open source lovers cackle with glee more than anything :)
      No, because you don't understand how embracing and extending works.
    4. Re:No surprise here... by arivanov · · Score: 4, Insightful

      He has been doing it long before that. This behaviour bares no relation to Novell.

      I think somebody needs to tell explain him some basics of of human relationships.

      If somebody blows you off the way Microsoft blew him off on a job interview the best way to deal with them is to reject them. They will come back sooner or later. In fact if you reject them a couple of time they will keep coming back with a better offer than you really deserve.

      The worst thing to do in cases like that is to try sticking your nose up their rectum the way he is constantly trying to do. In life that achieves the opposite. The person who rejected you in the first place will treat you exactly as you should be treated when you are in a naso-rectal interface position. Like shit.

      All I can say - what a daft jerk...

      --
      Baker's Law: Misery no longer loves company. Nowadays it insists on it
      http://www.sigsegv.cx/
    5. Re:No surprise here... by h4rm0ny · · Score: 4, Interesting


      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.
    6. Re:No surprise here... by Xtravar · · Score: 4, Insightful

      Why is everyone so opposed to taking MS's technology and running? They put a bunch of R&D into C# and its standard libraries, and then released it as an open specification.

      Mono is not and should not be treated as a compatibility layer.

      People complain that you'll never run Windows .Net apps properly on Linux... well, so? Does that make C# and .Net technology completely garbage? Not at all, and to believe that is foolish.

      Having a C# implementation in Linux, with a decent C# widget toolkit, is a good way to invite developers into the open source world. Going from [Visual Studio + C# + Windows.Forms] to [MonoDevelop + C# + GTK#] is a lot less daunting than to [emacs + C + GTK], etc.

      And it might just blow your mind, but using C# on Linux is sometimes the best language for the job, especially if you have to use C# at work.

      --
      Buckle your ROFL belt, we're in for some LOLs.
    7. Re:No surprise here... by Just+Some+Guy · · Score: 4, Insightful

      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!

      It's called "Python" (and also goes by the alias "Java"). Hence the complete lack of need for Mono - we already have that functionality in mature, well-tested languages.

      --
      Dewey, what part of this looks like authorities should be involved?
    8. Re:No surprise here... by Bloater · · Score: 5, Interesting

      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.

    9. Re:No surprise here... by Vexorian · · Score: 4, Interesting

      I feel that Mono, like Wine, should be treated as a compatibility layer to run software intended for other operating systems

      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"
    10. Re:No surprise here... by Vexorian · · Score: 4, Insightful
      it does not matter if it is cross platform or cross language, the intention is to make applications for the default Linux desktop...

      How is this dependant on MS..

      If Linux grew a MONO dependence, MS would get the turn off switch. In several situations MS has implied that MONO requires "patent protection", in the case of MS, it does not matter if their claims are utter BS or true, they got a bunch of lawyers and since they ACTUALLY invent .net in this case that gives them even more advantage.

      If MS didn't intend on suing regarding MONO, they wouldn't implicitly add protection for it on Novell's deal and at the same time deny protection to it on the next deals...

      Even if there weren't any patent threats, MS will keep upgrading .net and make sure MONO gets more and more obsolete, the idea would be to make Linux look like a second class citizen.

      if you aren't using MS's application stack (SWF, ASP.Net, etc.) and choose to use GTK# or MonoRails, then you are safe... if it runs under mono today, it should run under mono tomorrow... Maybe MS comes up with some new extensions to C#/.Net that aren't in the mono version.. so what... if I'm not developing a windows application, that doesn't affect me in the slightest... I don't get your position in that regard.

      Why would you need MS' application stack? beats me to find a logical reason to do that kind of stuff, if the intention with mono was to make a multilanguage cross platform framework that had nothing to do with .net , then I don't understand why the rush to clone .net ... Or where they totally unable to invent their own one?

      If they thought that you would be able to run .net apps as a bonus, then they are just crazy, for starters .net apps require at least windows forms (and there are a bunch of .net that also need active x garbage) and windows forms is not part of MS' 'freed' stuff.

      --

      Copyright infringement is "piracy" in the same way DRM is "consumer rape"
  2. What are the possibilities? by Anonymous Coward · · Score: 5, Insightful

    "Miguel de Icaza's widely-publicized praise for OOXML as a 'superb standard'"

    There is really only a few possibilities:
    1) The community is wrong and OOXML is really an open/good standard (heh)
    2) One of the heads of GNOME is so inept as not to be able to see that OOXML is far from being an open standard
    3) Icaza was bought off

    Or is it something else:
    4) ???

  3. Re:Quit looking for body snatchers by Dionysus · · Score: 5, Insightful

    What better way to lure Windows users away than to provide support for the formats their existing documents are probably already in? That's an argument for getting MS-doc support, not necessary MS-OOXML since it hasn't become a defacto standard yet. Supporting MS-OOXML is pretty much giving MS the power to make the standard.
    --
    Je ne parle pas francais.
  4. What the FUCK? by bjourne · · Score: 5, Interesting

    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.

    1. Re:What the FUCK? by rossendryv · · Score: 5, Informative

      As you can see for your self, GNOME is participating directly in the Standards process: http://www.ecma-international.org/memento/TC45-M.htm

  5. No proof by pembo13 · · Score: 4, Interesting

    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
  6. Patents are body snatchers. by Erris · · Score: 4, Insightful

    The reason Novell et the GNOME foundation are so involved is for simple compatibility reasons. What better way to lure Windows users away than to provide support for the formats their existing documents are probably already in?

    That sounds nice but it falls down when M$ sends in a clown car full of patent lawyers. That's one of the big reasons OOXML needs to be shot down by ISO. The others are a lack of completeness and 998 other technical problems. OOXML is not doing well in the marketplace and probably never will. If ever there was a case of wasted effort, OOXML is it. Resources are better spent making better ODF applications.

    As for a better way to lure Windows users, have you seen Vista?

    --
    DMCA, Hollings, Palladium. What might have sounded like paranoia is now common sense.
  7. Re:Who are you kidding? Or are you just trolling? by TheUnFounded · · Score: 4, Insightful

    I've been developing in C# for sometime now. I've also done extensive development in Java, PHP, and Perl. I can tell you that the .Net framework and Visual Studio is by FAR the most productive environment for developing desktop applications, and (in some instances) web apps.

    And you're complaining that someone is working to bring all the applications developed on the .Net framework, and the .Net development environment itself, to Linux?

    WTF is your problem? Are you really that stupid to think that interoperability with MS tools/frameworks is a BAD thing? How many people do you think would use Linux at ALL if Samba didn't allow communication to Windows boxes? Or what if there was no way to read/write an NTFS partition? Interoperability is key, and the task Miguel has undertaken is a good one. Quit complaining that someone's working to make Linux a more competitive OS.

  8. Another reason to use KDE by asm2750 · · Score: 5, Insightful

    " ... This "users are idiots, and are confused by functionality" mentality of Gnome is a disease ... Please, just tell people to use KDE." -- Linus Torvalds

  9. Re:Who are you kidding? Or are you just trolling? by rbanffy · · Score: 5, Insightful

    There may be more problems, but the one I like the most is "because it cedes control over how people develop software (C# and the .NET API) for a free platform (Mono) to Microsoft". With such control in hand, Microsoft can make the development as awkward or costly as they want. And in the unlikely hypothesis developers succeed, Microsoft may call in all their patents and make half of Gnome illegal in the US.

  10. Miguel is wrong, but not without reason by m2943 · · Score: 4, Interesting

    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.

  11. Holding their feet to the fire by jdub! · · Score: 5, Informative

    G'day,

    The background is really simple: While Jody Goldberg (Gnumeric maintainer extraordinaire) was at Novell, he had been doing rocking work on the ECMA committee to make sure OOXML didn't just slip through, under-specified and uninvestigated. Jody put them through the wringer!

    So, when Jody left Novell, the GNOME Foundation supported his participation on the ECMA working group, so he could continue to "keep the bastards honest". :-)

    The GNOME Foundation does not support ISO standardisation of OOXML. But whether or not that happens, we're still going to have to support Microsoft document formats, just like everyone else. Should we let Microsoft shove OOXML through ECMA without challenge? Hell no. That's why we have one of our best hackers in there, holding their feet to the fire.

    Thanks,

    - Jeff Waugh, GNOME Foundation Board

    (Given how often it comes up, I suppose it's also important to note that Miguel does not speak for the GNOME Foundation or the GNOME project in general.)

    1. Re:Holding their feet to the fire by segedunum · · Score: 4, Informative

      The GNOME Foundation does not support ISO standardisation of OOXML. But whether or not that happens, we're still going to have to support Microsoft document formats, just like everyone else. Should we let Microsoft shove OOXML through ECMA without challenge? Hell no. That's why we have one of our best hackers in there, holding their feet to the fire.
      I'm afraid that's not the way it's coming off:

      http://blogs.gnome.org/jody/2007/09/10/odf-vs-oox-asking-the-wrong-questions/

      Basically, he's telling us that OOXML is easier to support than ODF because they're just mapping the old binary format on to the new format. It comes off as an advertisement, which Stephane Rodriguez fortunately pours some cold water on. Microsoft is also using this to claim, extremely incorrectly, that Gnumeric has rich support for OOXML ( http://blogs.msdn.com/brian_jones/archive/2007/08/07/iwork-08-supports-the-open-xml-formats.aspx ), and is using Gnumeric as a poster for OOXML support:

      http://blogs.msdn.com/brian_jones/archive/2007/08/15/why-there-s-no-microsoft-in-open-xml.aspx

      But whether or not that happens, we're still going to have to support Microsoft document formats, just like everyone else.
      Yes, we have to support an existing and widely used binary format, because that's the format most documents are in...............it doesn't mean we have to support yet another format that is basically the same as the old one, except different, which very few people actually use. Let's concentrate on getting people off the old binary format and into ODF.

      Just because Microsoft uses something, it doesn't mean that anyone else has to support it. The paradox is that if they do start supporting it then they really will end up having to support a new Microsoft format, again, because it's just boosting it's popularity and installed base. Microsoft then starts using this as evidence that OOXML is an open standard that others can fully implement. We need to get out of this ridiculous cycle.
  12. Re:MOD PARENT UP by an.echte.trilingue · · Score: 4, Insightful
    I have mod moints, and I will not mod him up. Here's why:
    1. Miguel interviewed for a job at MS
      I've heard that, but without, oh I dunno... a reference, it isn't that informative.
    2. However, they could finance him to subvert linux
      Just one piece of evidence? Possibly an insightful statement... but conspiracy theories without evidence are little more than that.
    3. This is all documented information
      WHERE???
    4. He's the kind of guy they like -- not a US citizen and willing to work cheap
      That sounds like unfounded xenophobia to me. You have to have a reference for a statement like that. How much did he want? Was it less than an American doing his job would earn?
    The assertions are plausible, but without just one reference, one piece of evidence, it doesn't really advance the conversation any more than "LOL M$ suxors!!!111!"

    --
    weirdest thing I ever saw: scientology advertising on slashdot.
  13. You don't have to clone Windows... by argent · · Score: 4, Insightful

    You don't have to clone Windows to produce a viable alternative platform... and in fact if you do end up cloning Windows you'll have eliminated everything that makes the result "alternative".

    Why should I care about a Linux-based system where your applications are written in .NET and your formats and user interface and APIs are driven by compatibility with Windows? If I want to run an OS that's compatible with Windows, I've already got that option.

    What makes Linux an alternative is that it's an Open Systems environment that happens to be Open Source as well. That applications written for it aren't locked in to Linux, they'll run on any Open Systems platform. If the interfaces and protocols it uses are Microsoft's, then why should anyone care whether it's got a Linux or an NT kernel under the hood?

  14. Look at the score. by argent · · Score: 5, Informative

    And for the last two decades, people were pushing AT&T stuff, some of it patented.

    AT&T donated the key patent for UNIX (the setuid patent) into the public domain. The UNIX APIs were designed to be independent of the underlying hardware and implementation, and they never made any attempt to enforce any potential copyrights on the UNIX programmer's manuals. The only product I know of that felt it necessary to avoid using the precise APIs described in the manual, ever, was Idris... presumably because it was by a former Bell Labs employee. There are, so far as I can tell, only two significant operating systems started after the publication of the 1976 Bell System Technical Journal that were not based primarily on the UNIX "software tools" environment: Mac OS, and Windows... and both of those were instead based on the Xerox environment. I'm not counting MS-DOS, because it was an 8086 port of CP/M by Tim Patterson of Seattle Computer Systems, and starting with MS-DOS 2.x it was increasingly adopting UNIX APIs.

    By 1987 (two decades ago) the UNIX environment had been re-implemented dozens of times, both standalone and hosted on top of other operating systems. By 1997 (one decade ago) there was no operating system in the world that wasn't either UNIX-based, transitioning to UNIX, or shipping with a functional hosted UNIX environment... other than Windows.

    And by that time AT&T had sold all their rights in UNIX to Novell, who had publicly disclaimed any intellectual property in the APIs.

    If there was any remaining danger in these APIs, the results of the Caldera (the new SCO) suit have completely defanged it.

    So far, there is no indication that there is any more risk to Mono from Microsoft than there was to Linux from AT&T.

    On the one hand we have a set of APIs that were already in the public domain both because of explicit donation and due to being published without copyright notice before the US joined the Berne convention, and have since been been proven safe to use, and on the other hand we have a set of APIs that are actively controlled by a company that has a history of using submarine patents, and who is currently attempting to monetize them... with some success.

    If you can't see there is a difference there you're deliberately not looking at it.

  15. Re:De Icaza has already lost all his credibility by segedunum · · Score: 4, Informative

    The .NET platform is now controlled by Microsoft, but, as I understand it, it's more free than Java used to be a while back:
    Java is soon to be fully open sourced, and at least there was a full specification if you wanted to create your own version. With .Net, no such luck. What is in the ECMA stuff is exceptionally limited, and will not give you a working, compatible CLR. Indeed, much has had to be reverse engineered.
  16. Re:Who are you kidding? Or are you just trolling? by antiMStroll · · Score: 4, Insightful

    FFS, give it a rest guys: "Gutsy Gibbon is the code name for Ubuntu 7.10, the current Ubuntu release. It was released on 18 October 2007." What bearing a 10 day old distro release has on the role of NTFS write capability on the past decade's plus adoption of Linux is beyond me, but I'll leave you all to sort that out while I go shopping.

  17. Re:Quit looking for body snatchers by bcrowell · · Score: 5, Insightful

    Miguel's stated that, as a standard, OOXML is alright, but also shuddered at dealing with the way Microsoft abused binary segments in the format. The reason Novell et the GNOME foundation are so involved is for simple compatibility reasons. What better way to lure Windows users away than to provide support for the formats their existing documents are probably already in?

    Looking at some of de Icaza's recent posts on slashdot, I find them hard to reconcile with that innocent interpretation. His public statements about OOXML are wildly disingenuous; I can't see how anybody who understands the nature of the criticisms of OOXML could fail to see them as pure FUD.

    IMO, it would indicate a problem with GNOME if GNOME couldn't tolerate dissent on this issue, but it would also indicate a problem with the community if the community couldn't see through de Icaza's reality distortion field, and understand that he's saying ridiculous things because he has commercial ties to MS.

    In the OSS world, it's all about whuffie. De Icaza earned a lot of whuffie by founding GNOME and writing a lot of code. In my eyes, he's lost it all by failing to be forthright.

  18. Re:Why not boycott Gnome? Who needs it? by Kjella · · Score: 5, Insightful

    Want to make a GPL-only fork of Qt? Go right ahead, Trolltech won't do a thing to stop you. In fact, up until the latest 4.3.2 release there was first a big project to port Qt3 to Windows, then a small one to add the compiler support to Qt4 that was missing compared to the commercial version and Trolltech never complained. But if you want Trolltech do to something for you, like adopt your source into their tree and maintain it, they're asking for something in return - that they can sell it for closed source software as well. I don't get your sense of entitlement, do you demand Linus accept your code as well? Or are they perfectly free to ask for something in return, or just to tell you to fuck off? Yes, they are.

    Trolltech delivers a kick-ass platform for open-source development. They do it for free under the GPL, using their own paid developers to do it. How do they get paid? Well, they've found a way to make closed-source companies pay them for the use of their code. Who are you crying for? Those poor companies? That you can't ruin their business model by forcing them to take code they can't sell that way? That you have to run your own fork/patch set? Oh cry me a river... no, YOU go to hell. I bet Trolltech has done 1000x times as much for open source as you ever have.

    --
    Live today, because you never know what tomorrow brings
  19. The more the Merrier by Jody+Goldberg · · Score: 5, Insightful

    While working for Novell I was able to join both OASIS for ODF and ECMA for OOX. After leaving the OO.o development team at Novell to return to other work I lost both memberships and had to scramble to rejoin. Maintaing Gnumeric is a hobby, and my current employer is not involved in the standardization process. Paying out the membership costs of either OASIS or ECMA was not going to happen at the personal or corporate level. Thankfully there was a non-profit tier available, and the GNOME Foundation generously sponsored me to re-join ECMA and TC45 to continue to participate in the the specification process. After spending the last 8 years playing proctologist to every spreadsheet format around, and complaining loudly at the poor quality of documentation for XLS it seems ridiculous to pass up the opportunity to engage MS, and ensure that the spec of their new format was more detailed than previous efforts.

    My personal opinion (not speaking for the GNOME foundation or past or present employers) is that both specs should be standards
          http://www.gnome.org/~jody/files/2007-ON-Linux-Beyond-ISO-Dome.pdf

    The FLOSS community is going to need to implement importers for both formats to help our users, and I'll be happiest when both OOX and ODF are significantly clearer. 5700 pages of OOX is too _short_, Likewise the 700 + 300 (Open formula) in ODF is far too short. Lets double the size of OOX (although with better formatting the number of pages would likely be unchanged), and lets quadruple the level of detail in ODF to get it into a useful state. I only wish that ODF had undergone a fraction of the review that OOX has seen.

    This is not about GNOME endorsing OOX, it's about GNOME doing the work necessary for users. There should be reps from Sun's OO.o team on the ECMA TC, and MS reps in the ODF meetings. The goal of this process is to produce useful documentation, and it takes an implementor to know where the really important details are. It hardly seems in the best interest of the FLOSS community to leave the standardization efforts up to corporate interests at Microsoft, Sun, or IBM.

    1. Re:The more the Merrier by jhol13 · · Score: 4, Insightful

      Why?

      Why should there be two standards for essentially one thing?

      If more the merrier, why not 200? This would of course mean not a single one gets adopted.
      If less is better what does OOXML bring that is useful to the users and other developers (non Gnumeric)? So useful that developers have to implement support for both, so good a support that user's are not inconvenienced?

      You are in the position to say how big task it is to support both instead of one and if it is really worthwhile effort, not me. I am just asking.