<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Snarky Comments</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/02/07/snarky-comments.aspx</link><description>My last blog posting was in a tone that was a bit too snarky for my tastes. I was writing late, and tired - and that is never a good combination. Readers of the blog have, in the past, asked me to maintain a more level tone given the issues I'm addressing.</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Snarky Comments</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/02/07/snarky-comments.aspx#1622616</link><pubDate>Thu, 08 Feb 2007 02:51:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1622616</guid><dc:creator>Dennis E. Hamilton</dc:creator><description>&lt;p&gt;Good, because I recommend you as an exemplar of level-headedness to my friends who want to know what the fuss is all about.&lt;/p&gt;
&lt;p&gt;Of course, I don't have to be quite so polite: &lt;a rel="nofollow" target="_new" href="http://orcmid.com/blog/2007/02/latest-oox-odf-fud-spat-states-prepare.asp"&gt;http://orcmid.com/blog/2007/02/latest-oox-odf-fud-spat-states-prepare.asp&lt;/a&gt;&lt;/p&gt;</description></item><item><title>re: Snarky Comments</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/02/07/snarky-comments.aspx#1625710</link><pubDate>Thu, 08 Feb 2007 12:43:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1625710</guid><dc:creator>Stephane Rodriguez</dc:creator><description>&lt;p&gt;Jason said &amp;quot;The Open XML Translator is now in production, and delivers interoperability.&amp;quot;&lt;/p&gt;
&lt;p&gt;What do you mean to imply here? Do you mean that because this component is running on say ONE physical customer site, it is ready for mass consumption?&lt;/p&gt;
&lt;p&gt;That is a gross mischaracterization of not just that case, but of software deployment principles in general.&lt;/p&gt;
&lt;p&gt;It is quite possible that the component meets the needs of some customer. After all, it does not process air, right? But you cannot extrapolate to all customer needs out there, especially when on the one hand Microsoft themselves say that customers out there use 10% of MS Office products, all different 10%, on the other hand the list of supported features by this component is arbitrarily limited.&lt;/p&gt;
&lt;p&gt;Who made that list?&lt;/p&gt;</description></item><item><title>re: Snarky Comments</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/02/07/snarky-comments.aspx#1625745</link><pubDate>Thu, 08 Feb 2007 12:51:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1625745</guid><dc:creator>Stephane Rodriguez</dc:creator><description>&lt;p&gt;Jason said &amp;quot;The difference there has been that our motivations have always been rather transparent, we'd like to see broad adoption of Office.&amp;quot;&lt;/p&gt;
&lt;p&gt;No.&lt;/p&gt;
&lt;p&gt;Back in 2000, in the WYSIWYG HTML era, Office 2000 shipped along with proprietary IE extensions (markup language, and a proprietary rendering run-time) known as V.M.L.&lt;/p&gt;
&lt;p&gt;(that's perhaps the only time the Office product group worked with the IE product group in the whole history of Office.)&lt;/p&gt;
&lt;p&gt;There is a BillG exhibit in the IOWA consumer case that mentions that MS Office &amp;quot;must be the only platform able to render Office documents, on top of Windows&amp;quot;.&lt;/p&gt;
&lt;p&gt;Hence VML. When creating HTML documents from Office 2000, the MSO semantics (proprietary) are translated into VML markup that only IE can render.&lt;/p&gt;
&lt;p&gt;What you did, in the name of HTML standards, was probably because you cared about interoperability, right?&lt;/p&gt;
&lt;p&gt;No wonder Office 2007 documents contain not just those VML parts (instead of DrawingML parts), but there are new VML parts introduced. Meaning that Microsoft does not intend to kill their old strategy by a long shot. &lt;/p&gt;</description></item><item><title>re: Snarky Comments</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/02/07/snarky-comments.aspx#1626543</link><pubDate>Thu, 08 Feb 2007 14:18:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1626543</guid><dc:creator>Zaine Ridling</dc:creator><description>&lt;p&gt;Hey, at least you're in the game and contributing. Beyond control, it seems evident that many governments see ODF as an opportunity to save money. When you look at their terribly slow upgrade cycles (how many, e.g., are still stuck on Office 97?), you soon see how daunting the cost of converting their systems and data are. Add in a new file format, and they feel stunned in the face of sticker shock at the task.&lt;/p&gt;</description></item><item><title>re: Snarky Comments</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/02/07/snarky-comments.aspx#1627300</link><pubDate>Thu, 08 Feb 2007 16:58:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1627300</guid><dc:creator>JasonG</dc:creator><description>&lt;p&gt;Hey, maybe the ODF supporters will stop posting snarky comments as well?&lt;/p&gt;</description></item><item><title>re: Snarky Comments</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/02/07/snarky-comments.aspx#1629199</link><pubDate>Thu, 08 Feb 2007 22:26:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1629199</guid><dc:creator>Ben Langhinrichs</dc:creator><description>&lt;p&gt;I guess my one objection to the whole process by which the Office Open XML standard has been developed is that there was such resistance to suggestions and over-reliance on what seemed easiest for the current code to work. &amp;nbsp;Even in places where it seems almost certain to come back to haunt Microsoft, the easy way was chosen.&lt;/p&gt;
&lt;p&gt;As a small software developer, I don't &amp;quot;favor&amp;quot; ODF and &amp;quot;not favor&amp;quot; Office Open XML as much as I favor the approach taken in developing and modifying ODF. &amp;nbsp;I wish that Microsoft could get together with OASIS and develop a comprehensive standard that would allow true interoperability and support for legacy documents. &amp;nbsp;It would certainly be a lot easier than the current chore of developing for both ODF and OOXML, without a lot of rational explanation about why they shouldn't be made one. &lt;/p&gt;
&lt;p&gt;So, aside from IBM's stake in the game, we independent software developers would be better off if you and IBM were to get off your high horses and work together. &amp;nbsp;Then we could all serve our mutual customers better. &amp;nbsp;At the moment, the ODF standard is a heck of a lot easier to support, so it will tend to &amp;quot;win&amp;quot; resources, but the Microsoft Office dominance means it forces us to develop for that too. &amp;nbsp;It is just a pain in the neck, and doesn't lead me to feel all too happy with either side. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;I really don't understand why Microsoft couldn't have just supported and extended ODF when it had a chance, but I guess that horse is out of the stable now.&lt;/p&gt;</description></item><item><title>re: Snarky Comments</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/02/07/snarky-comments.aspx#1634065</link><pubDate>Fri, 09 Feb 2007 14:18:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1634065</guid><dc:creator>Philip Storry</dc:creator><description>&lt;p&gt;One quick suggestion - if you can, at least edit the previous entry to put a link to this post at the top of the page. Otherwise, the two entries stand pretty much alone to the casual passerby, and may not give the impression you wanted.&lt;/p&gt;</description></item><item><title>re: Snarky Comments</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/02/07/snarky-comments.aspx#1655054</link><pubDate>Mon, 12 Feb 2007 01:49:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1655054</guid><dc:creator>jasonmatusow</dc:creator><description>&lt;p&gt;Got it Philip - I will make the change. &lt;/p&gt;
&lt;p&gt;Ben, thank you for your comment. I can imagine that the clash of the titans, while good fodder for the media and the blogosphere, is painful for that smaller ISVs. &amp;nbsp;I wish I could see a silver bullet in this, but I don't. Commercial interests in this one are very strong with literally billions of dollars in the mix. IBM does not want to go back and recode all the work they are doing on Notes to support OpenXML. Microsoft had already been going down the Open XML path (back in the pre-Office 2003 days). Also, the architectural decisions behind the two formats are very different (verbose vs. abbreviated XML etc.).&lt;/p&gt;
&lt;p&gt;There is never an easy answer - and clearly self-interest by many parties is going to continue to push hard on the whole discussion. As Stephanie points out in her comment, factors of marketplace competition drive all of the participants. &lt;/p&gt;
&lt;p&gt;The good news is that the underlying move to XML by most players is very strong. Interoperability is more of a design goal for everyone now than it has ever been. The trending is positive.&lt;/p&gt;
&lt;p&gt;Jason&lt;/p&gt;
</description></item><item><title>re: Snarky Comments</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/02/07/snarky-comments.aspx#1660122</link><pubDate>Mon, 12 Feb 2007 14:27:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1660122</guid><dc:creator>James Governor</dc:creator><description>&lt;p&gt;heavy-handed tactics and rhetoric? i think its called corporate strategy isn't it? I am pretty sure I have seen some rhetoric from Microsoft in my time.&lt;/p&gt;
&lt;p&gt;fwiw Jason I think you would gain even more credibility by linking to some non-Microsoft bloggers. &amp;nbsp;Your blogroll is very whitebread. perhaps a link to Rick Jelliffe? ;-)&lt;/p&gt;
&lt;p&gt;Just to be self-serving for a moment I do tend to think you could call out Stephen's blog. I know you read it and take it seriously. &amp;nbsp;&lt;/p&gt;</description></item><item><title>re: Snarky Comments</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/02/07/snarky-comments.aspx#1662682</link><pubDate>Mon, 12 Feb 2007 20:30:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1662682</guid><dc:creator>jasonmatusow</dc:creator><description>&lt;p&gt;James - thanks. Yes, you are right about the fact that I should be linked to many voices. I am bad about putting time into my blog and this is one of the things that is important for me to update. I take many people's blogs seriously - those from Redmonk more than most. &lt;/p&gt;
&lt;p&gt;Yes - I agree completely about the rhetoric being about corporate strategy. That has been my point all along. &lt;/p&gt;
&lt;p&gt;Jason&lt;/p&gt;
</description></item><item><title>re: Snarky Comments</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/02/07/snarky-comments.aspx#1664549</link><pubDate>Tue, 13 Feb 2007 01:26:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1664549</guid><dc:creator>jasonmatusow</dc:creator><description>&lt;p&gt;James - I added some folks that I like to read to my site. And yes, my site is very whitebread. &amp;lt;sigh&amp;gt;&lt;/p&gt;
&lt;p&gt;Jason&lt;/p&gt;
</description></item><item><title>re: Snarky Comments</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/02/07/snarky-comments.aspx#1671605</link><pubDate>Wed, 14 Feb 2007 01:21:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1671605</guid><dc:creator>Ben Langhinrichs</dc:creator><description>&lt;p&gt;Jason - I would agree completely that the general trend towards XML formats is strongly positive, no matter how this particular skirmish turns out. - Ben&lt;/p&gt;</description></item></channel></rss>