<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Risks and Rewards</title>
	<atom:link href="http://www.schwieb.com/blog/2008/10/23/risks-and-rewards/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards</link>
	<description>Random blatherings</description>
	<lastBuildDate>Thu, 11 Mar 2010 20:50:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: laeeq</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35933</link>
		<dc:creator>laeeq</dc:creator>
		<pubDate>Wed, 21 Oct 2009 08:55:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35933</guid>
		<description>This issue is almost fixed in the latest version. Check Apple site for info.

&lt;a href=&quot;http://blog.macmasters.net&quot; rel=&quot;nofollow&quot;&gt;MacMasters&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>This issue is almost fixed in the latest version. Check Apple site for info.</p>
<p><a href="http://blog.macmasters.net" rel="nofollow">MacMasters</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35913</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Mon, 20 Jul 2009 16:59:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35913</guid>
		<description>You want a simple fix .... just don&#039;t combine every single palette into one global all knowing toolbox.  The formatting palette should be its own palette.  Everything else can be thrown into a second pallete (that no one will ever use).  That way you don&#039;t have to use multiple windows on a single toolbox.  

The simplest solution is usually the best solution.  If Spaces doesn&#039;t support multiple grouped windows, don&#039;t use multiple grouped windows!</description>
		<content:encoded><![CDATA[<p>You want a simple fix &#8230;. just don&#8217;t combine every single palette into one global all knowing toolbox.  The formatting palette should be its own palette.  Everything else can be thrown into a second pallete (that no one will ever use).  That way you don&#8217;t have to use multiple windows on a single toolbox.  </p>
<p>The simplest solution is usually the best solution.  If Spaces doesn&#8217;t support multiple grouped windows, don&#8217;t use multiple grouped windows!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35911</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Sun, 28 Jun 2009 22:08:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35911</guid>
		<description>Ok, fault-finding aside, can we expect this to be fixed (or quickly fixable) in Snow Leopard?  Sorry if this is an ignorant question, but this is the first good detailed discussion of this I&#039;ve seen-- it&#039;s just a little outside of my non-engineer competence.</description>
		<content:encoded><![CDATA[<p>Ok, fault-finding aside, can we expect this to be fixed (or quickly fixable) in Snow Leopard?  Sorry if this is an ignorant question, but this is the first good detailed discussion of this I&#8217;ve seen&#8211; it&#8217;s just a little outside of my non-engineer competence.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35910</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Sat, 27 Jun 2009 17:48:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35910</guid>
		<description>&quot;And why the hell is there no VBA? Is it that hard?&quot;

Yeah, it is actually. I would argue that the reasons are mostly self-inflicted, but it&#039;s still a non-trivial task. If it makes you feel better, VBA support is supposed to come back in the next version (Office 2011? IDK).

http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/
http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/</description>
		<content:encoded><![CDATA[<p>&#8220;And why the hell is there no VBA? Is it that hard?&#8221;</p>
<p>Yeah, it is actually. I would argue that the reasons are mostly self-inflicted, but it&#8217;s still a non-trivial task. If it makes you feel better, VBA support is supposed to come back in the next version (Office 2011? IDK).</p>
<p><a href="http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/" rel="nofollow">http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/</a><br />
<a href="http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/" rel="nofollow">http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mojo</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35909</link>
		<dc:creator>Mojo</dc:creator>
		<pubDate>Wed, 10 Jun 2009 16:24:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35909</guid>
		<description>The spaces/toolbar problem could be solved so easily. I guess there is some kind of event that is raised before/when the space changes. Just hde the toolbar or make word inactive (eg. focus finder) and it won&#039;t get moved to the next space. If you use cmd-tab to jump to another application on a different space, the toolbar doesn&#039;t get moved because the app is activated, word is deactivated and the toolbar is hidden ...

What was said about performance has nothing to do with 30000 pixels or what so ever. Sometimes I feel like being near a singularity because word is so slow. Add a picture and then wait a few seconds before it is drawn. There a plenty of other situation, where the speed just sucks. And my documents are not even big. Just admit it, the codebase is a mess. The implementation is just bad! Making such an ugly hacked toolbar ... Why not using a plane dumb window?

Bad rendering - texts are jumping back from the next side just to be not really there, where one can see them. You have to scroll up and down to make word redraw the entire area correctly. Clicking on the scrollbar doesn&#039;t bring you to the corresponding area in the document, though the scrollbar grabber(how is this thing called?) gets moved to that place. For you microsoft people who don&#039;t know that: there are two options in the system preferences! Clicking to the scrollbar can really mean to scroll to that place (like on windows) or really jumpt there!

And why the hell is there no VBA? Is it that hard? This is one of THE BIG REASONS to use MS office.

As I first used the I was totally shocked. How can such a big and powerful company like MS bring such crap to the market? Did anybody test this? Then the first updates came out (promising perfomance improvements, etc ...) and I couldn&#039;t install them, because the installer didn&#039;t find my MS installation ... Such things MUST NOT HAPPEN! Shame on you, really!

If openoffice wouldn&#039;t bad so bad I&#039;d use it. But unfortunately it&#039;s slow, has bad rendering, bad usability. So why do I still use office 2008? Because I need to have compatibility to windows office 2003/2007. That&#039;s the only reason ...</description>
		<content:encoded><![CDATA[<p>The spaces/toolbar problem could be solved so easily. I guess there is some kind of event that is raised before/when the space changes. Just hde the toolbar or make word inactive (eg. focus finder) and it won&#8217;t get moved to the next space. If you use cmd-tab to jump to another application on a different space, the toolbar doesn&#8217;t get moved because the app is activated, word is deactivated and the toolbar is hidden &#8230;</p>
<p>What was said about performance has nothing to do with 30000 pixels or what so ever. Sometimes I feel like being near a singularity because word is so slow. Add a picture and then wait a few seconds before it is drawn. There a plenty of other situation, where the speed just sucks. And my documents are not even big. Just admit it, the codebase is a mess. The implementation is just bad! Making such an ugly hacked toolbar &#8230; Why not using a plane dumb window?</p>
<p>Bad rendering &#8211; texts are jumping back from the next side just to be not really there, where one can see them. You have to scroll up and down to make word redraw the entire area correctly. Clicking on the scrollbar doesn&#8217;t bring you to the corresponding area in the document, though the scrollbar grabber(how is this thing called?) gets moved to that place. For you microsoft people who don&#8217;t know that: there are two options in the system preferences! Clicking to the scrollbar can really mean to scroll to that place (like on windows) or really jumpt there!</p>
<p>And why the hell is there no VBA? Is it that hard? This is one of THE BIG REASONS to use MS office.</p>
<p>As I first used the I was totally shocked. How can such a big and powerful company like MS bring such crap to the market? Did anybody test this? Then the first updates came out (promising perfomance improvements, etc &#8230;) and I couldn&#8217;t install them, because the installer didn&#8217;t find my MS installation &#8230; Such things MUST NOT HAPPEN! Shame on you, really!</p>
<p>If openoffice wouldn&#8217;t bad so bad I&#8217;d use it. But unfortunately it&#8217;s slow, has bad rendering, bad usability. So why do I still use office 2008? Because I need to have compatibility to windows office 2003/2007. That&#8217;s the only reason &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35908</link>
		<dc:creator>Steven</dc:creator>
		<pubDate>Wed, 10 Jun 2009 03:06:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35908</guid>
		<description>Schwieb, your post is all well and good. But why not just tell the blunt truth to everyone; 1) PowerPlant is in use all over Office, and 2) such code was NEVER supposed to make it to Intel.

Your team had plenty of time to re-implement plenty of Office over to Cocoa, and at least pure Carbon. I can&#039;t even begin to imagine what kind of job it was to wrap PowerPlant inside Carbon so it would compile on Intel. Sadly, such a feat is extremely impressive (and extremely time-wasting). Software Engineering 101 tells us that if we need to spend 8 months porting someone else&#039;s (Metrowerks) product so we don&#039;t have to rewrite ours, YOU&#039;RE DOING IT WRONG! 

So instead of doing the responsible thing and creating a decent product, Office sucks, and people are finally starting to give it up in favor of OpenOffice and iWork.

Way to go MS!</description>
		<content:encoded><![CDATA[<p>Schwieb, your post is all well and good. But why not just tell the blunt truth to everyone; 1) PowerPlant is in use all over Office, and 2) such code was NEVER supposed to make it to Intel.</p>
<p>Your team had plenty of time to re-implement plenty of Office over to Cocoa, and at least pure Carbon. I can&#8217;t even begin to imagine what kind of job it was to wrap PowerPlant inside Carbon so it would compile on Intel. Sadly, such a feat is extremely impressive (and extremely time-wasting). Software Engineering 101 tells us that if we need to spend 8 months porting someone else&#8217;s (Metrowerks) product so we don&#8217;t have to rewrite ours, YOU&#8217;RE DOING IT WRONG! </p>
<p>So instead of doing the responsible thing and creating a decent product, Office sucks, and people are finally starting to give it up in favor of OpenOffice and iWork.</p>
<p>Way to go MS!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35899</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 18 May 2009 16:05:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35899</guid>
		<description>Damn Right!!!

Why is it that Adobe products do no suffer the same issues??</description>
		<content:encoded><![CDATA[<p>Damn Right!!!</p>
<p>Why is it that Adobe products do no suffer the same issues??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35898</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Thu, 14 May 2009 21:59:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35898</guid>
		<description>Spaces Fixed in 10.5.7 :D</description>
		<content:encoded><![CDATA[<p>Spaces Fixed in 10.5.7 <img src='http://www.schwieb.com/blog/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jani</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35895</link>
		<dc:creator>Jani</dc:creator>
		<pubDate>Sat, 09 May 2009 12:41:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35895</guid>
		<description>Hi, and thanks for this very eye opening post. Thank you also for this detailed explanations about the Spaces bug. The point is, it is not the costumers task to forgive the big Microsoft Company any incompetence! We pay Microsoft a LOT of money and we expect performance!

I must totaly agree with Eliezer and nearly all the other posts here. 

1. The Spaces bug makes Office 2008 unusable.

2. Noone cares who&#039;s fault this bug is, MS Apple or whoever.

3. Spaces is perhaps the most important new feature in Leopard. So there is no question that Office 2008 must work with it perfectly.

4. If rewriting the whole Toolbox code in Cocoa is the only way to fix it,- then damn!!! just do it! You should have started to write everything in Cocoa 6 years ago. We pay a lot of money for this office suit so use it to fix this bug! We don&#039;t care if you have not enough software engineers. Just hire more. You are the big Microsoft. So why should the Windows Office crew be much bigger then the apple crew? The point is no one cares how big the effort is to fix this bug. Just fix it and do it fast. Even freeware like Neooffice can handle spaces... It&#039;s a shame for MS.

Sorry for being so rude. But attitude of Microsoft is just embarrassing.</description>
		<content:encoded><![CDATA[<p>Hi, and thanks for this very eye opening post. Thank you also for this detailed explanations about the Spaces bug. The point is, it is not the costumers task to forgive the big Microsoft Company any incompetence! We pay Microsoft a LOT of money and we expect performance!</p>
<p>I must totaly agree with Eliezer and nearly all the other posts here. </p>
<p>1. The Spaces bug makes Office 2008 unusable.</p>
<p>2. Noone cares who&#8217;s fault this bug is, MS Apple or whoever.</p>
<p>3. Spaces is perhaps the most important new feature in Leopard. So there is no question that Office 2008 must work with it perfectly.</p>
<p>4. If rewriting the whole Toolbox code in Cocoa is the only way to fix it,- then damn!!! just do it! You should have started to write everything in Cocoa 6 years ago. We pay a lot of money for this office suit so use it to fix this bug! We don&#8217;t care if you have not enough software engineers. Just hire more. You are the big Microsoft. So why should the Windows Office crew be much bigger then the apple crew? The point is no one cares how big the effort is to fix this bug. Just fix it and do it fast. Even freeware like Neooffice can handle spaces&#8230; It&#8217;s a shame for MS.</p>
<p>Sorry for being so rude. But attitude of Microsoft is just embarrassing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eliezer</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35894</link>
		<dc:creator>Eliezer</dc:creator>
		<pubDate>Fri, 01 May 2009 19:24:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35894</guid>
		<description>Thanks for the explanation on the bug. I understand that this is a problem at the root of how windows are displayed in Mac OS X, and its a difficult one to solve.

The problem is that I don&#039;t care, and neither do any of the other users of Office 2008. The fact that you have difficult software engineering problems is nothing new; all software companies have difficult software engineering problems, that&#039;s the nature of programming. Even more so, this isn&#039;t something you should be even discussing on a public blog. It sounds to me like you&#039;re saying, &quot;this is difficult, so we aren&#039;t doing it.&quot; Apple introduced Cocoa and Carbon almost a decade ago at this point, and even back then they had a roadmap which ended with a completely cocoa-based interface.

Microsoft has had plenty of time to work on a complete rewrite, as Adobe did a few years back. It seems that they chose not to go this route, and now they&#039;re stuck with the bad choice of either continuing with sluggish and buggy software or committing to a multi-year rewrite process after everyone else has already adapted to the new software design. Either way, customers are unhappy and Microsoft loses out as people switch away from their software.</description>
		<content:encoded><![CDATA[<p>Thanks for the explanation on the bug. I understand that this is a problem at the root of how windows are displayed in Mac OS X, and its a difficult one to solve.</p>
<p>The problem is that I don&#8217;t care, and neither do any of the other users of Office 2008. The fact that you have difficult software engineering problems is nothing new; all software companies have difficult software engineering problems, that&#8217;s the nature of programming. Even more so, this isn&#8217;t something you should be even discussing on a public blog. It sounds to me like you&#8217;re saying, &#8220;this is difficult, so we aren&#8217;t doing it.&#8221; Apple introduced Cocoa and Carbon almost a decade ago at this point, and even back then they had a roadmap which ended with a completely cocoa-based interface.</p>
<p>Microsoft has had plenty of time to work on a complete rewrite, as Adobe did a few years back. It seems that they chose not to go this route, and now they&#8217;re stuck with the bad choice of either continuing with sluggish and buggy software or committing to a multi-year rewrite process after everyone else has already adapted to the new software design. Either way, customers are unhappy and Microsoft loses out as people switch away from their software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35890</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 24 Apr 2009 03:17:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35890</guid>
		<description>Adobe and Microsoft should jointly run a technical blog called: &quot;Don&#039;t blame us, Apple did it.&quot;  Granted, Adobe and Microsoft hate each other.  But they share quite a bit of camaraderie, having both stuck with the Mac platform through thick-and-thin, ever since the Classic 68k days.  Never mind Mac Office and Spaces -- you should read some of the flames that Adobe got for 64-bit Photoshop.

Mac Office is falling farther and farther behind Win Office.  Frankly, the one-year offset doesn&#039;t seem to be enough to keep up.  Wasn&#039;t so bad back in the days of Mac Office 98.  But ever since the x86 transition, Mac BU seems to be putting out fires and punting ever more features to the next version.  Meanwhile, Win Office is not standing still.  And considering that Adobe took a one-version development hit for Cocoa ...</description>
		<content:encoded><![CDATA[<p>Adobe and Microsoft should jointly run a technical blog called: &#8220;Don&#8217;t blame us, Apple did it.&#8221;  Granted, Adobe and Microsoft hate each other.  But they share quite a bit of camaraderie, having both stuck with the Mac platform through thick-and-thin, ever since the Classic 68k days.  Never mind Mac Office and Spaces &#8212; you should read some of the flames that Adobe got for 64-bit Photoshop.</p>
<p>Mac Office is falling farther and farther behind Win Office.  Frankly, the one-year offset doesn&#8217;t seem to be enough to keep up.  Wasn&#8217;t so bad back in the days of Mac Office 98.  But ever since the x86 transition, Mac BU seems to be putting out fires and punting ever more features to the next version.  Meanwhile, Win Office is not standing still.  And considering that Adobe took a one-version development hit for Cocoa &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35889</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Tue, 21 Apr 2009 07:26:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35889</guid>
		<description>Sorry to sound like just another flamer. But I count my upgrade from 2004 to 2008 as a waste of money. 
Besides the still unresolved issues with spaces, slow startup etc., there is the annoying tendency of Entourage 2008 to rebuild its database on reboot, preventing you to access your Emails for the first 10 minutes after booting your Mac. Then the removal of 2004&#039;s &quot;Empty cache command&quot;, which was a lifesaver, if you were unable to open an IMAP folder in Entourage 2004. The still existing &quot;Repair Message List&quot; command is not a full substitute.

As a consequence, I&#039;ve reverted to 2004 (except Powerpoint, where the new features slightly outweigh the introduced bugs). 2008 is still installed on my Mac and I give it a try with each dot-release (like today), but so far none of my big issues with 2008 have been solved.

Frankly I don&#039;t believe any more we will see these things get fixed in Office 2008.  More likely there will be a complete rewrite (Cocoa ?) as Office 2010, 2012, ...

Sad for those, who spent their money already on 2008!</description>
		<content:encoded><![CDATA[<p>Sorry to sound like just another flamer. But I count my upgrade from 2004 to 2008 as a waste of money.<br />
Besides the still unresolved issues with spaces, slow startup etc., there is the annoying tendency of Entourage 2008 to rebuild its database on reboot, preventing you to access your Emails for the first 10 minutes after booting your Mac. Then the removal of 2004&#8217;s &#8220;Empty cache command&#8221;, which was a lifesaver, if you were unable to open an IMAP folder in Entourage 2004. The still existing &#8220;Repair Message List&#8221; command is not a full substitute.</p>
<p>As a consequence, I&#8217;ve reverted to 2004 (except Powerpoint, where the new features slightly outweigh the introduced bugs). 2008 is still installed on my Mac and I give it a try with each dot-release (like today), but so far none of my big issues with 2008 have been solved.</p>
<p>Frankly I don&#8217;t believe any more we will see these things get fixed in Office 2008.  More likely there will be a complete rewrite (Cocoa ?) as Office 2010, 2012, &#8230;</p>
<p>Sad for those, who spent their money already on 2008!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raaul</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35888</link>
		<dc:creator>Raaul</dc:creator>
		<pubDate>Thu, 16 Apr 2009 19:33:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35888</guid>
		<description>Alright, I understand everything involved in plotting lots of points repeatedly, even if they fall on the same pixel.  Sure, you could devise a fancy, novel way of reducing the number of points to trace.  But before we talk about dramatic innovation to fix the problem, why don&#039;t we first take a look to the past, when functionality already existed?  How does the Windows &#039;07 version of Excel do this differently that my same chart traces/retraces up to 100&#039;s of times faster?  How did 2004 for Mac do it, where again, it still traces in a dramatically shorter period of time?  This is an issue that arose in 2008.  Is there a reason why the fix isn&#039;t as simple as removing whatever steps took the overall process from functional to dysfunctional?</description>
		<content:encoded><![CDATA[<p>Alright, I understand everything involved in plotting lots of points repeatedly, even if they fall on the same pixel.  Sure, you could devise a fancy, novel way of reducing the number of points to trace.  But before we talk about dramatic innovation to fix the problem, why don&#8217;t we first take a look to the past, when functionality already existed?  How does the Windows &#8216;07 version of Excel do this differently that my same chart traces/retraces up to 100&#8217;s of times faster?  How did 2004 for Mac do it, where again, it still traces in a dramatically shorter period of time?  This is an issue that arose in 2008.  Is there a reason why the fix isn&#8217;t as simple as removing whatever steps took the overall process from functional to dysfunctional?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Edwards</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35886</link>
		<dc:creator>Steven Edwards</dc:creator>
		<pubDate>Sun, 05 Apr 2009 21:19:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35886</guid>
		<description>Alright, I&#039;m back with some insight.

If you want an example of a &quot;toolbox&quot;-like window that behaves well, check out the &quot;Table...&quot; item in the Text Edit menus. It opens up a little window that&#039;s used for formating tables, and you can have tables open in multiple text edit docs at the same time, SWITCHING BETWEEN SPACES, and doing whatever you want... and it&#039;s fine with it.

It might not look as flashy as the MS Office toolbox, but damn, it works.</description>
		<content:encoded><![CDATA[<p>Alright, I&#8217;m back with some insight.</p>
<p>If you want an example of a &#8220;toolbox&#8221;-like window that behaves well, check out the &#8220;Table&#8230;&#8221; item in the Text Edit menus. It opens up a little window that&#8217;s used for formating tables, and you can have tables open in multiple text edit docs at the same time, SWITCHING BETWEEN SPACES, and doing whatever you want&#8230; and it&#8217;s fine with it.</p>
<p>It might not look as flashy as the MS Office toolbox, but damn, it works.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Edwards</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35885</link>
		<dc:creator>Steven Edwards</dc:creator>
		<pubDate>Sat, 04 Apr 2009 23:08:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35885</guid>
		<description>For the most part, I like the toolbox.

But I&#039;m willing to keep it closed if it will stop Spaces from spazzing out.

The problem is, it doesn&#039;t.

Here&#039;s an example of what happened to me before. I was working on a Word Doc in Space 2. Then I switched to Space 1 to refer to the Word doc there. I began reading it. About five full seconds later, I magically get switched back to Space 2. I wasn&#039;t even touching the keyboard or the mouse. I don&#039;t understand how the hell it happened.

But it happens to me a lot with Word.

And my toolbox is closed the entire time :(</description>
		<content:encoded><![CDATA[<p>For the most part, I like the toolbox.</p>
<p>But I&#8217;m willing to keep it closed if it will stop Spaces from spazzing out.</p>
<p>The problem is, it doesn&#8217;t.</p>
<p>Here&#8217;s an example of what happened to me before. I was working on a Word Doc in Space 2. Then I switched to Space 1 to refer to the Word doc there. I began reading it. About five full seconds later, I magically get switched back to Space 2. I wasn&#8217;t even touching the keyboard or the mouse. I don&#8217;t understand how the hell it happened.</p>
<p>But it happens to me a lot with Word.</p>
<p>And my toolbox is closed the entire time <img src='http://www.schwieb.com/blog/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Palmer</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35884</link>
		<dc:creator>Mike Palmer</dc:creator>
		<pubDate>Tue, 31 Mar 2009 19:16:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35884</guid>
		<description>I appreciate the explanation, but is there really no workaround? E.g., stick the toolbox contents permanently in the main document window? (I wish there was an option for this anyway to avoid multiple floating windows.)

Or, I wish Word could automatically minimize the toolbox before Spaces switches, that would also reduce the problem I suspect.

We are paying customers after all, and the bug has been around at least a year (more)? Right? This must be your biggest single bug. You should at least try to reduce the impact.

Thanks.

P.S. BTW my own workaround is to set up Command+T to toggle the toolbox open and closed. If you keep it closed all the time, it seems like the problem happens much less often. (I have not empirically measured but seems like it.) Go to Tools-&gt;Customize Keyboard. In the View category there is the command ToggleOfficeToolbox, which you can tie to whatever keyboard shortcut you like.</description>
		<content:encoded><![CDATA[<p>I appreciate the explanation, but is there really no workaround? E.g., stick the toolbox contents permanently in the main document window? (I wish there was an option for this anyway to avoid multiple floating windows.)</p>
<p>Or, I wish Word could automatically minimize the toolbox before Spaces switches, that would also reduce the problem I suspect.</p>
<p>We are paying customers after all, and the bug has been around at least a year (more)? Right? This must be your biggest single bug. You should at least try to reduce the impact.</p>
<p>Thanks.</p>
<p>P.S. BTW my own workaround is to set up Command+T to toggle the toolbox open and closed. If you keep it closed all the time, it seems like the problem happens much less often. (I have not empirically measured but seems like it.) Go to Tools-&gt;Customize Keyboard. In the View category there is the command ToggleOfficeToolbox, which you can tie to whatever keyboard shortcut you like.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barry Wainwright</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35883</link>
		<dc:creator>Barry Wainwright</dc:creator>
		<pubDate>Tue, 31 Mar 2009 10:58:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35883</guid>
		<description>Marvin:
&quot;Another thing I fail to understand is why Entourage is SUCH a far-cry from Outlook and why the data files are not inter-compatible. Thus far, no one from the MacBU seems to have addressed this&quot;

The why is easily answered - it&#039;s because Entourage was designed from the ground up as a completely different application. It has added Exchange functionality that has improved with each release, but it is NOT outlook! See this page for details:
</description>
		<content:encoded><![CDATA[<p>Marvin:<br />
&#8220;Another thing I fail to understand is why Entourage is SUCH a far-cry from Outlook and why the data files are not inter-compatible. Thus far, no one from the MacBU seems to have addressed this&#8221;</p>
<p>The why is easily answered &#8211; it&#8217;s because Entourage was designed from the ground up as a completely different application. It has added Exchange functionality that has improved with each release, but it is NOT outlook! See this page for details:</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marvin</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35866</link>
		<dc:creator>Marvin</dc:creator>
		<pubDate>Fri, 27 Mar 2009 02:47:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35866</guid>
		<description>I was glad to see Office 2008 come to life, myself.  I do have to wonder, however, *why* any of the Office 2008 applications are glacially slow to load.  I know that one of the reasons the Windows version, 2007 (and even 2003), is able to load so quickly is that, by default, Office is partially loaded at boot.  2008 should at least *offer* this functionality.  The 2008 applications take SO long to boot (on an otherwise incredibly speedy new MacBook Pro with 4 gigs of RAM) that I have had to resort to iWork to do anything that I need to do *now* rather than later.

Another thing I fail to understand is why Entourage is SUCH a far-cry from Outlook and why the data files are not inter-compatible.  Thus far, no one from the MacBU seems to have addressed this.

Outside of just basic performance-enhancement, are ACTUAL speed increases something Microsoft is going to be able to do with 2008?</description>
		<content:encoded><![CDATA[<p>I was glad to see Office 2008 come to life, myself.  I do have to wonder, however, *why* any of the Office 2008 applications are glacially slow to load.  I know that one of the reasons the Windows version, 2007 (and even 2003), is able to load so quickly is that, by default, Office is partially loaded at boot.  2008 should at least *offer* this functionality.  The 2008 applications take SO long to boot (on an otherwise incredibly speedy new MacBook Pro with 4 gigs of RAM) that I have had to resort to iWork to do anything that I need to do *now* rather than later.</p>
<p>Another thing I fail to understand is why Entourage is SUCH a far-cry from Outlook and why the data files are not inter-compatible.  Thus far, no one from the MacBU seems to have addressed this.</p>
<p>Outside of just basic performance-enhancement, are ACTUAL speed increases something Microsoft is going to be able to do with 2008?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brookie</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35864</link>
		<dc:creator>Brookie</dc:creator>
		<pubDate>Thu, 26 Mar 2009 00:50:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35864</guid>
		<description>Please make this more transparant. 

I&#039;m a big apple fan, but I&#039;m more than aware that their coding is far from perfect!

They&#039;re also very secretive about what they&#039;re working on, which perhaps works for iPods, but really frustrates the end user when all we want to know is that our frustration is being channelled into something productive when we give feedback. 

Please do all that you can to make this more visible. Knowing that there is some intelligable reason as to why these two interfaces are not working really helps a frustrated user. 

I had to look right down to the third page of comments on something from the second page of google to hear that there was something not quite right with the implementation of spaces. Spread the word and reduce stress levels; Spaces is not perfect yet and the amount of time required to fix the problem is not financially viable right now. *sigh of relief*</description>
		<content:encoded><![CDATA[<p>Please make this more transparant. </p>
<p>I&#8217;m a big apple fan, but I&#8217;m more than aware that their coding is far from perfect!</p>
<p>They&#8217;re also very secretive about what they&#8217;re working on, which perhaps works for iPods, but really frustrates the end user when all we want to know is that our frustration is being channelled into something productive when we give feedback. </p>
<p>Please do all that you can to make this more visible. Knowing that there is some intelligable reason as to why these two interfaces are not working really helps a frustrated user. </p>
<p>I had to look right down to the third page of comments on something from the second page of google to hear that there was something not quite right with the implementation of spaces. Spread the word and reduce stress levels; Spaces is not perfect yet and the amount of time required to fix the problem is not financially viable right now. *sigh of relief*</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35862</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Fri, 13 Mar 2009 00:07:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35862</guid>
		<description>&quot;From my perspective, the bug makes Office 2008 (especially Word and Excel) almost unusable.&quot;

AMEN - and here in March of 2009, it still is almost unusable. How this continues, just blows my mind.</description>
		<content:encoded><![CDATA[<p>&#8220;From my perspective, the bug makes Office 2008 (especially Word and Excel) almost unusable.&#8221;</p>
<p>AMEN &#8211; and here in March of 2009, it still is almost unusable. How this continues, just blows my mind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Lau</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35861</link>
		<dc:creator>Dan Lau</dc:creator>
		<pubDate>Tue, 10 Mar 2009 16:13:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35861</guid>
		<description>Office 2008 isn&#039;t the only app making use of window groups and having issues with Spaces: http://adobegripes.tumblr.com/post/85046860/adobe-and-the-fake-windows

That anonymous source does sound mighty familiar!</description>
		<content:encoded><![CDATA[<p>Office 2008 isn&#8217;t the only app making use of window groups and having issues with Spaces: <a href="http://adobegripes.tumblr.com/post/85046860/adobe-and-the-fake-windows" rel="nofollow">http://adobegripes.tumblr.com/post/85046860/adobe-and-the-fake-windows</a></p>
<p>That anonymous source does sound mighty familiar!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: clf</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35858</link>
		<dc:creator>clf</dc:creator>
		<pubDate>Tue, 24 Feb 2009 16:18:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35858</guid>
		<description>Like J, I also think you can make the Spaces issue manageable by fixing the Toolbox. Unlike the Mac BU team though, my solution would be to kill the Toolbox completely. Really. It&#039;s a mess. You have 95% of the program commands crammed into a single panel in a tiny, floating window that &quot;helpfully&quot; auto-collapses when it loses focus. What if I might want to go right back to that set of buttons again? You&#039;re needlessly increasing the number of mouse-clicks needed to do anything important. It frustrates the hell out of me, and that isn&#039;t even taking into account the fact that the Toolbox floats above the other Word windows, often covering up parts of the document I am working on or at a minimum blocking access to the scrollbar handle. Add in that most of the panels in the Toolbox are darn near useless - honestly, aside from the Formatting palette I have never used any of the other options - can you begin to see why this Toolbox is a useless mess?

Every time I go home and work on my Windows machine, running Office 07, it just drives home exactly how awful the Office 08 interface really is. The Ribbon and pop-up context menu are ridiculously simple yet manage to give me quick, ready access to 90% of the commands I need, often without moving my mouse more than an inch. The Ribbon interface feels more Mac-like to me than anything I&#039;ve seen in Mac Office, ever, and I started using Mac Word in 1992.

Also, while you&#039;re at it, can you make Excel stop changing the size of open windows every time I switch between them? It drives me batty. Respect the window size I choose, don&#039;t change it. Ever.

PowerPoint, I give you props there. It honestly is the only Office 08 program that seems to work as expected, with essentially no issues. Great job. Now can you make the rest work as well? We&#039;re waiting, and we&#039;re losing patience.</description>
		<content:encoded><![CDATA[<p>Like J, I also think you can make the Spaces issue manageable by fixing the Toolbox. Unlike the Mac BU team though, my solution would be to kill the Toolbox completely. Really. It&#8217;s a mess. You have 95% of the program commands crammed into a single panel in a tiny, floating window that &#8220;helpfully&#8221; auto-collapses when it loses focus. What if I might want to go right back to that set of buttons again? You&#8217;re needlessly increasing the number of mouse-clicks needed to do anything important. It frustrates the hell out of me, and that isn&#8217;t even taking into account the fact that the Toolbox floats above the other Word windows, often covering up parts of the document I am working on or at a minimum blocking access to the scrollbar handle. Add in that most of the panels in the Toolbox are darn near useless &#8211; honestly, aside from the Formatting palette I have never used any of the other options &#8211; can you begin to see why this Toolbox is a useless mess?</p>
<p>Every time I go home and work on my Windows machine, running Office 07, it just drives home exactly how awful the Office 08 interface really is. The Ribbon and pop-up context menu are ridiculously simple yet manage to give me quick, ready access to 90% of the commands I need, often without moving my mouse more than an inch. The Ribbon interface feels more Mac-like to me than anything I&#8217;ve seen in Mac Office, ever, and I started using Mac Word in 1992.</p>
<p>Also, while you&#8217;re at it, can you make Excel stop changing the size of open windows every time I switch between them? It drives me batty. Respect the window size I choose, don&#8217;t change it. Ever.</p>
<p>PowerPoint, I give you props there. It honestly is the only Office 08 program that seems to work as expected, with essentially no issues. Great job. Now can you make the rest work as well? We&#8217;re waiting, and we&#8217;re losing patience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35855</link>
		<dc:creator>J</dc:creator>
		<pubDate>Tue, 03 Feb 2009 17:25:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35855</guid>
		<description>I think you could at least make this problem manageable by fixing the Toolbox.  If you assign Word to say Space 1 then you will not experience any problems with main Word window and switching spaces, but you will still experience issue with the bottom part of the tool box.  The fact that you are using a windows group for the formatting palette is just sloppy coding in my opinion (You clearly reused the toolbox code from 2004 in 2008).  However i think you could make a very simple fix to the problem: when a user switches spaces you should kill the the toolbar window and when a user a user switches back to the space and brings word into focus you should reinitiate the toolbar.</description>
		<content:encoded><![CDATA[<p>I think you could at least make this problem manageable by fixing the Toolbox.  If you assign Word to say Space 1 then you will not experience any problems with main Word window and switching spaces, but you will still experience issue with the bottom part of the tool box.  The fact that you are using a windows group for the formatting palette is just sloppy coding in my opinion (You clearly reused the toolbox code from 2004 in 2008).  However i think you could make a very simple fix to the problem: when a user switches spaces you should kill the the toolbar window and when a user a user switches back to the space and brings word into focus you should reinitiate the toolbar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mason</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35847</link>
		<dc:creator>mason</dc:creator>
		<pubDate>Fri, 16 Jan 2009 20:39:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35847</guid>
		<description>Thanks for reaching out to me via twitter to explain my Spaces/Toolbar issues. It&#039;s great to understand where the problem is coming from. Just something I&#039;ll have to deal with for now.</description>
		<content:encoded><![CDATA[<p>Thanks for reaching out to me via twitter to explain my Spaces/Toolbar issues. It&#8217;s great to understand where the problem is coming from. Just something I&#8217;ll have to deal with for now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elf</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35843</link>
		<dc:creator>Elf</dc:creator>
		<pubDate>Thu, 18 Dec 2008 22:46:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35843</guid>
		<description>It&#039;s not much of a secret that most business user of MacOS would be using Windows if it wasn&#039;t for Office for Mac.  So for that I&#039;m grateful that MS supports OS/X with these products.  In fact, I wish they would do the same for Visio if there&#039;s any business case for it.  So while there are cracks in the some of aspects of the UI, overall Office 2008 is the rosetta stone we need if we want something other than Windows machines.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not much of a secret that most business user of MacOS would be using Windows if it wasn&#8217;t for Office for Mac.  So for that I&#8217;m grateful that MS supports OS/X with these products.  In fact, I wish they would do the same for Visio if there&#8217;s any business case for it.  So while there are cracks in the some of aspects of the UI, overall Office 2008 is the rosetta stone we need if we want something other than Windows machines.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35831</link>
		<dc:creator>Charles</dc:creator>
		<pubDate>Wed, 12 Nov 2008 21:23:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35831</guid>
		<description>Funny you&#039;re comment about using OpenOffice. I was so used to Office 2003 on windows, I found that OpenOffice.org 3 actually was more like 2003 than 2008. Therefore, I used what I was familiar with.</description>
		<content:encoded><![CDATA[<p>Funny you&#8217;re comment about using OpenOffice. I was so used to Office 2003 on windows, I found that OpenOffice.org 3 actually was more like 2003 than 2008. Therefore, I used what I was familiar with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aram</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35828</link>
		<dc:creator>Aram</dc:creator>
		<pubDate>Sun, 26 Oct 2008 17:12:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35828</guid>
		<description>You got me wrong. I am not against LDAP at all. I am talking about the support for GAL lookups without LDAP, the functionality that is available even on iPhone (as well as Windows Mobile). Companies normally provide LDAP support inside (due to AD being actually an extension to LDAP). But they are normally reluctant to have the same LDAP server published to the Internet, even with all the security attached. That&#039;s why many of us suffer from not being able to access GAL working from outside. Yes, there is VPN, but that is too much trouble for such a basic thing as mail communication.</description>
		<content:encoded><![CDATA[<p>You got me wrong. I am not against LDAP at all. I am talking about the support for GAL lookups without LDAP, the functionality that is available even on iPhone (as well as Windows Mobile). Companies normally provide LDAP support inside (due to AD being actually an extension to LDAP). But they are normally reluctant to have the same LDAP server published to the Internet, even with all the security attached. That&#8217;s why many of us suffer from not being able to access GAL working from outside. Yes, there is VPN, but that is too much trouble for such a basic thing as mail communication.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35827</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sun, 26 Oct 2008 15:50:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35827</guid>
		<description>&lt;blockquote&gt;Yes, Entourage obviously needs some improvement to better service current needs of people. We can’t afford its terrible handling of HTML, its inability to lookup Exchange contacts without involving LDAP, incompatibility with Time Machine, etc. All these things are well known. But for the rest of it: is there anything in Entourage that really needs to be fully redone?&lt;/blockquote&gt;

I&#039;d rather have E&#039;rage&#039;s handling of directory lookups via a single, consistent, standard mechanism than Outlook&#039;s completely split personality handling of Exchange and LDAP. LDAP use in Outlook blows chunks, and there&#039;s a lot of LDAP out there, *especially* in the Mac userbase, something E&#039;rage does have to deal with.

LDAP is an approved, supported way to interact with Exchange&#039;s GAL, so the fact that E&#039;rage uses it is not bad by any definition. The *implementation* could use some fixing, but LDAP is not &quot;bad&quot;.</description>
		<content:encoded><![CDATA[<blockquote><p>Yes, Entourage obviously needs some improvement to better service current needs of people. We can’t afford its terrible handling of HTML, its inability to lookup Exchange contacts without involving LDAP, incompatibility with Time Machine, etc. All these things are well known. But for the rest of it: is there anything in Entourage that really needs to be fully redone?</p></blockquote>
<p>I&#8217;d rather have E&#8217;rage&#8217;s handling of directory lookups via a single, consistent, standard mechanism than Outlook&#8217;s completely split personality handling of Exchange and LDAP. LDAP use in Outlook blows chunks, and there&#8217;s a lot of LDAP out there, *especially* in the Mac userbase, something E&#8217;rage does have to deal with.</p>
<p>LDAP is an approved, supported way to interact with Exchange&#8217;s GAL, so the fact that E&#8217;rage uses it is not bad by any definition. The *implementation* could use some fixing, but LDAP is not &#8220;bad&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35826</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Sun, 26 Oct 2008 15:12:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35826</guid>
		<description>I think you&#039;re underestimating the impact of the Spaces bug, as if it were some cosmetic fix that would impact other important functionality. From my perspective, the bug makes Office 2008 (especially Word and Excel) almost unusable. 

I know a bug of this type is an interaction between the operating system and the application, but it sounds really, really lame to say &quot;It&#039;s Apple&#039;s fault&quot; when a) almost no other applications have this behavior, and b) you&#039;ve had a year to fix it.

At any rate, thanks for explaining the issues, and for your comment on  my blog.</description>
		<content:encoded><![CDATA[<p>I think you&#8217;re underestimating the impact of the Spaces bug, as if it were some cosmetic fix that would impact other important functionality. From my perspective, the bug makes Office 2008 (especially Word and Excel) almost unusable. </p>
<p>I know a bug of this type is an interaction between the operating system and the application, but it sounds really, really lame to say &#8220;It&#8217;s Apple&#8217;s fault&#8221; when a) almost no other applications have this behavior, and b) you&#8217;ve had a year to fix it.</p>
<p>At any rate, thanks for explaining the issues, and for your comment on  my blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aram</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F10%2F23%2Frisks-and-rewards%2F&amp;seed_title=Risks+and+Rewards/comment-page-1/#comment-35824</link>
		<dc:creator>Aram</dc:creator>
		<pubDate>Sat, 25 Oct 2008 13:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35824</guid>
		<description>My belief is that old apps should look and feel like old apps. They should never get modern and should never undergo a face-lifting with the sole goal to hide old scratches. For a small utility a major overhaul might be a proper thing to do. For such a complex piece of engineering such as Office, the most of development work should be to keep it running and keep it being as useful as it was 10 years ago. From that standpoint Office 2008 is good enough. All the rest is a marketing fluff that has nothing to do with user needs. Go ask Photoshop people if they want the thing to be all Cocoa. Their answer will be: “keep my hotkeys, keep the behavior, make it faster with ever growing image sizes, make it use larger memory, add more intelligence behind the scene and I’ll be happy”. Why we, veteran users of MS Office, are constantly asking for some major change? What for? 

Yes, Entourage obviously needs some improvement to better service current needs of people. We can’t afford its terrible handling of HTML, its inability to lookup Exchange contacts without involving LDAP, incompatibility with Time Machine, etc. All these things are well known. But for the rest of it: is there anything in Entourage that really needs to be fully redone? 

All in all I believe MS Office for Mac is an excellent piece of software, very well crafted, obviously worth the money. I tried other options several times (such as OpenOffice). Always switched back to MS Office at the end.</description>
		<content:encoded><![CDATA[<p>My belief is that old apps should look and feel like old apps. They should never get modern and should never undergo a face-lifting with the sole goal to hide old scratches. For a small utility a major overhaul might be a proper thing to do. For such a complex piece of engineering such as Office, the most of development work should be to keep it running and keep it being as useful as it was 10 years ago. From that standpoint Office 2008 is good enough. All the rest is a marketing fluff that has nothing to do with user needs. Go ask Photoshop people if they want the thing to be all Cocoa. Their answer will be: “keep my hotkeys, keep the behavior, make it faster with ever growing image sizes, make it use larger memory, add more intelligence behind the scene and I’ll be happy”. Why we, veteran users of MS Office, are constantly asking for some major change? What for? </p>
<p>Yes, Entourage obviously needs some improvement to better service current needs of people. We can’t afford its terrible handling of HTML, its inability to lookup Exchange contacts without involving LDAP, incompatibility with Time Machine, etc. All these things are well known. But for the rest of it: is there anything in Entourage that really needs to be fully redone? </p>
<p>All in all I believe MS Office for Mac is an excellent piece of software, very well crafted, obviously worth the money. I tried other options several times (such as OpenOffice). Always switched back to MS Office at the end.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
