<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Office 2008, slips to 2008</title>
	<atom:link href="http://www.maccast.com/2007/08/02/office-2008-slips-to-2008/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.maccast.com/2007/08/02/office-2008-slips-to-2008/</link>
	<description>For MacGeeks by MacGeeks</description>
	<pubDate>Sat, 22 Nov 2008 04:48:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Rene</title>
		<link>http://www.maccast.com/2007/08/02/office-2008-slips-to-2008/#comment-50164</link>
		<dc:creator>Rene</dc:creator>
		<pubDate>Fri, 03 Aug 2007 17:18:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.maccast.com/2007/08/02/office-2008-slips-to-2008/#comment-50164</guid>
		<description>As I understand it, for the Intel transition, everyone needs to use Apple's Xcode. While this is a fine suite for small and medium-size developers, it seems to be a pain in the backside for large software companies, such as Adobe and Microsoft Mac BU.

So, please, don't blame Adobe or Microsoft, nor Apple, but the fact that it takes a long time to switch from other development suites to Xcode. The software has to be tailored to suite large development environments and programmers have to be educated to be efficient in programming in Xcode. That just takes a long time and introduces delays in the development cycles.</description>
		<content:encoded><![CDATA[<p>As I understand it, for the Intel transition, everyone needs to use Apple&#8217;s Xcode. While this is a fine suite for small and medium-size developers, it seems to be a pain in the backside for large software companies, such as Adobe and Microsoft Mac BU.</p>
<p>So, please, don&#8217;t blame Adobe or Microsoft, nor Apple, but the fact that it takes a long time to switch from other development suites to Xcode. The software has to be tailored to suite large development environments and programmers have to be educated to be efficient in programming in Xcode. That just takes a long time and introduces delays in the development cycles.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iMaki</title>
		<link>http://www.maccast.com/2007/08/02/office-2008-slips-to-2008/#comment-50118</link>
		<dc:creator>iMaki</dc:creator>
		<pubDate>Fri, 03 Aug 2007 06:09:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.maccast.com/2007/08/02/office-2008-slips-to-2008/#comment-50118</guid>
		<description>Not that I really care, but it appears neither Apple nor Microsoft has the ability to meet any deadline these days. They need to understand that delays in technology are among the most irritating and unforgiving factors in customer retention. My hope is iWork 08 will make us all forget about MS Office 2008. Regardless, I, for one, am disappointed by the never-ending failures to meet deadlines. One thing for sure, patience is not a strong-point of a typical Mac user, of which I am. Everything that has happened during Ballmer's reign has been a disappointment. This is just the latest iteration of a permanent trend with Microsoft.</description>
		<content:encoded><![CDATA[<p>Not that I really care, but it appears neither Apple nor Microsoft has the ability to meet any deadline these days. They need to understand that delays in technology are among the most irritating and unforgiving factors in customer retention. My hope is iWork 08 will make us all forget about MS Office 2008. Regardless, I, for one, am disappointed by the never-ending failures to meet deadlines. One thing for sure, patience is not a strong-point of a typical Mac user, of which I am. Everything that has happened during Ballmer&#8217;s reign has been a disappointment. This is just the latest iteration of a permanent trend with Microsoft.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
