<?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: &#8220;Dear Adobe&#8230;&#8221;</title>
	<atom:link href="http://blogs.adobe.com/jnack/2008/08/dear_adobe.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.adobe.com/jnack/2008/08/dear_adobe.html</link>
	<description></description>
	<lastBuildDate>Tue, 18 Jun 2013 23:17:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Bobby Dimitt</title>
		<link>http://blogs.adobe.com/jnack/2008/08/dear_adobe.html#comment-78518</link>
		<dc:creator>Bobby Dimitt</dc:creator>
		<pubDate>Tue, 07 May 2013 11:57:45 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/08/dear-adobe.html#comment-78518</guid>
		<description><![CDATA[I think one could make a case either way. I seem to recall that when the Big 10 finished their season before Thanksgiving, they had teams that would steadily move up the polls as other teams played a game the next week, then the conf championships would knock a few others down a peg. Say, a team would be at 6 or 7, then find themselves in the top 3-4 by the time everyone else beat up on one another. A downside was that by the time the bowls came around, they had not played for 50 days, but they cashed the check nonetheless.]]></description>
		<content:encoded><![CDATA[<p>I think one could make a case either way. I seem to recall that when the Big 10 finished their season before Thanksgiving, they had teams that would steadily move up the polls as other teams played a game the next week, then the conf championships would knock a few others down a peg. Say, a team would be at 6 or 7, then find themselves in the top 3-4 by the time everyone else beat up on one another. A downside was that by the time the bowls came around, they had not played for 50 days, but they cashed the check nonetheless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles</title>
		<link>http://blogs.adobe.com/jnack/2008/08/dear_adobe.html#comment-37271</link>
		<dc:creator>Charles</dc:creator>
		<pubDate>Thu, 15 Sep 2011 19:40:31 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/08/dear-adobe.html#comment-37271</guid>
		<description><![CDATA[I used CS2 for many years without issue - did exactly what it said on the tin - no more no less. Unfortunately, when I had to upgrade my PC, CS2 no longer worked, so I reluctantly (and expensively) upgraded to CS5. Needless to say, this has proved an expensive nightmare! Talk about &#039;full of shit&#039; - CS5 has cost me ten-fold what I paid for it in productivity nightmares, on the basis that there&#039;s so much shit in it I&#039;ll never use and the Adobe Community pops up, everytime I want to do a certain function. I require a full refund and compensation for the lost revenue and heartache. BTW: This is the &#039;clean&#039; version!!!]]></description>
		<content:encoded><![CDATA[<p>I used CS2 for many years without issue &#8211; did exactly what it said on the tin &#8211; no more no less. Unfortunately, when I had to upgrade my PC, CS2 no longer worked, so I reluctantly (and expensively) upgraded to CS5. Needless to say, this has proved an expensive nightmare! Talk about &#8216;full of shit&#8217; &#8211; CS5 has cost me ten-fold what I paid for it in productivity nightmares, on the basis that there&#8217;s so much shit in it I&#8217;ll never use and the Adobe Community pops up, everytime I want to do a certain function. I require a full refund and compensation for the lost revenue and heartache. BTW: This is the &#8216;clean&#8217; version!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aerin</title>
		<link>http://blogs.adobe.com/jnack/2008/08/dear_adobe.html#comment-9016</link>
		<dc:creator>Aerin</dc:creator>
		<pubDate>Tue, 16 Dec 2008 12:24:42 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/08/dear-adobe.html#comment-9016</guid>
		<description><![CDATA[I just got a big shock today when I tried to upgrade from Dreamweaver MX 2004 to CS4. Turns out that because Dreamweaver MX 2004 was part of a suite, I can&#039;t upgrade just that one application! The sales rep could give me no logical explanation (just that it was Adobe &quot;policy,&quot; even if it didn&#039;t make any sense). He also suggested that I should have known about Adobe&#039;s upgrade policy when I bought MX 2004 Studio -- which would have been a trick, because I bought it from Macromedia. I didn&#039;t need most of the suite, but bought it because it included both Dreamweaver and Freehand -- only to discover that Freehand had been ruined (in response to a lawsuit by Adobe, natch). Instead, I&#039;m still using Freehand 8 in the Mac Classic environment. So Dreamweaver is the only app in the suite I have been using, but I can&#039;t upgrade it for $199. My choices are to buy it new for $399 or upgrade to the CS4 Design suite for $599. (I currently have the CS2 Design suite.) I don&#039;t need to upgrade Photoshop, Acrobat, or InDesign (the apps I use in that suite). All I need to upgrade is Dreamweaver. I don&#039;t understand why I can&#039;t. Shouldn&#039;t &quot;downgrading&quot; from a suite to an application be possible? And even less expensive than &quot;upgrading&quot; the entire suite? And I can&#039;t even get Customer Service to give me the name and title of someone in Adobe customer relations to whom I can complain in an actual letter. (The people in India with whom I have spoken either have hung up on me or claimed that there is no such position, department, or function at Adobe and no address to which complaints about policy can be sent. Right. I&#039;ve found this site, read all the posts here, and written this note all while on hold for a supervisor while Adobe Customer Service waits for me to give up and hang up. )
]]></description>
		<content:encoded><![CDATA[<p>I just got a big shock today when I tried to upgrade from Dreamweaver MX 2004 to CS4. Turns out that because Dreamweaver MX 2004 was part of a suite, I can&#8217;t upgrade just that one application! The sales rep could give me no logical explanation (just that it was Adobe &#8220;policy,&#8221; even if it didn&#8217;t make any sense). He also suggested that I should have known about Adobe&#8217;s upgrade policy when I bought MX 2004 Studio &#8212; which would have been a trick, because I bought it from Macromedia. I didn&#8217;t need most of the suite, but bought it because it included both Dreamweaver and Freehand &#8212; only to discover that Freehand had been ruined (in response to a lawsuit by Adobe, natch). Instead, I&#8217;m still using Freehand 8 in the Mac Classic environment. So Dreamweaver is the only app in the suite I have been using, but I can&#8217;t upgrade it for $199. My choices are to buy it new for $399 or upgrade to the CS4 Design suite for $599. (I currently have the CS2 Design suite.) I don&#8217;t need to upgrade Photoshop, Acrobat, or InDesign (the apps I use in that suite). All I need to upgrade is Dreamweaver. I don&#8217;t understand why I can&#8217;t. Shouldn&#8217;t &#8220;downgrading&#8221; from a suite to an application be possible? And even less expensive than &#8220;upgrading&#8221; the entire suite? And I can&#8217;t even get Customer Service to give me the name and title of someone in Adobe customer relations to whom I can complain in an actual letter. (The people in India with whom I have spoken either have hung up on me or claimed that there is no such position, department, or function at Adobe and no address to which complaints about policy can be sent. Right. I&#8217;ve found this site, read all the posts here, and written this note all while on hold for a supervisor while Adobe Customer Service waits for me to give up and hang up. )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stib</title>
		<link>http://blogs.adobe.com/jnack/2008/08/dear_adobe.html#comment-9015</link>
		<dc:creator>stib</dc:creator>
		<pubDate>Sat, 11 Oct 2008 21:10:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/08/dear-adobe.html#comment-9015</guid>
		<description><![CDATA[I think the lack of market for Linux is purely a chicken and egg issue. I would switch to Linux in a heartbeat if I could run my Adobe apps on it. The reasons for preferring Linux are for another forum, but the main reason for not using it is the lack of &quot;real&quot; software for it, with potatoshop being the most oft cited example.
The elephant in the room is Open Source. For example, I got sick of waiting half an hour for the acrobat reader to load every time I wanted to look at a pdf, so I went looking for a replacement. The Sumatra PDF reader is coded by one person, and is a 1.2 megabyte application that does the same job, but better. What have the people in the acrobat reader department been doing all these years?
My point is that if open-source apps like these start doing adobe type things better then people are not going to be nearly as receptive to crap like the overseas pricing scam for long. And they&#039;ll discover that Adobe isn&#039;t the only game in town.
]]></description>
		<content:encoded><![CDATA[<p>I think the lack of market for Linux is purely a chicken and egg issue. I would switch to Linux in a heartbeat if I could run my Adobe apps on it. The reasons for preferring Linux are for another forum, but the main reason for not using it is the lack of &#8220;real&#8221; software for it, with potatoshop being the most oft cited example.<br />
The elephant in the room is Open Source. For example, I got sick of waiting half an hour for the acrobat reader to load every time I wanted to look at a pdf, so I went looking for a replacement. The Sumatra PDF reader is coded by one person, and is a 1.2 megabyte application that does the same job, but better. What have the people in the acrobat reader department been doing all these years?<br />
My point is that if open-source apps like these start doing adobe type things better then people are not going to be nearly as receptive to crap like the overseas pricing scam for long. And they&#8217;ll discover that Adobe isn&#8217;t the only game in town.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://blogs.adobe.com/jnack/2008/08/dear_adobe.html#comment-9014</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 01 Oct 2008 06:45:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/08/dear-adobe.html#comment-9014</guid>
		<description><![CDATA[John, I owe you an apology: for badgering you about Adobe&#039;s international pricing policy and their clear unwillingness to address the issue.
Now that I&#039;ve done a little research into the subject, I see that it&#039;s absolutely standard practise to charge more for software (and some hardware) over in Europe at least. I found an article going back to 1992 using the phrase &#039;price gouging&#039; - an ugly-sounding term which, since it has a specific legal meaning in some States, is something I won&#039;t accuse Adobe of.
Since the current type of pricing policy &lt;i&gt;is&lt;/i&gt; standard practise, Adobe would be crazy not to follow suit. Some companies are absolutely fair and charge the equivalent price (before taxes and allowing for currency fluctuations) in all markets. Others charge a premium of 10% to 20% for, ahem, &#039;localisation&#039;, something most European users would be comfortable with. Not happy, but OK with it. But Adobe&#039;s policy with CS3 and it appears CS4 is &lt;i&gt;not&lt;/i&gt; fair, reasonable or &#039;OK&#039;. The  differences make no sense until you realise that Adobe think that the European market will bear the price they&#039;re charging.
The big corporate market probably will. But most small to medium businesses aren&#039;t that wealthy and not that stupid: if it&#039;s cheaper to buy at the US price, that&#039;s what they&#039;ll do... I wonder how many US-purchased licenses are actually operating in Europe? (NB most continental Europeans involved in the Media speak excellent English: a native-language version may be perceived as an expensive luxury). And let&#039;s not get into the whole P2P thing.
The simple fact that a lot of software used in Europe is actually the US version tilts all sorts of statistics - including the sort of statistics companies use to justify their international pricing policies. This pushes us into a vicious spiral, one which I think has already started. It&#039;s up to Adobe to sort it out. By all means charge us Europeans a little more for all the reasons that software companies confronted with this practise fall back on (none of which stand up to close scrutiny). Most of us will give you the benefit of the doubt. There&#039;ll always be some who buy US versions simply because they&#039;re a bit cheaper. Adobe need to get their pricing structure organised to the point where, for most of us over here, it makes more sense to &#039;buy local&#039;.
If pricing was fairer, it would also take away one of the &#039;justifications&#039; used by the P2P brigade. That would lead to less people going down that route. That would mean them actually paying money for their software.
]]></description>
		<content:encoded><![CDATA[<p>John, I owe you an apology: for badgering you about Adobe&#8217;s international pricing policy and their clear unwillingness to address the issue.<br />
Now that I&#8217;ve done a little research into the subject, I see that it&#8217;s absolutely standard practise to charge more for software (and some hardware) over in Europe at least. I found an article going back to 1992 using the phrase &#8216;price gouging&#8217; &#8211; an ugly-sounding term which, since it has a specific legal meaning in some States, is something I won&#8217;t accuse Adobe of.<br />
Since the current type of pricing policy <i>is</i> standard practise, Adobe would be crazy not to follow suit. Some companies are absolutely fair and charge the equivalent price (before taxes and allowing for currency fluctuations) in all markets. Others charge a premium of 10% to 20% for, ahem, &#8216;localisation&#8217;, something most European users would be comfortable with. Not happy, but OK with it. But Adobe&#8217;s policy with CS3 and it appears CS4 is <i>not</i> fair, reasonable or &#8216;OK&#8217;. The  differences make no sense until you realise that Adobe think that the European market will bear the price they&#8217;re charging.<br />
The big corporate market probably will. But most small to medium businesses aren&#8217;t that wealthy and not that stupid: if it&#8217;s cheaper to buy at the US price, that&#8217;s what they&#8217;ll do&#8230; I wonder how many US-purchased licenses are actually operating in Europe? (NB most continental Europeans involved in the Media speak excellent English: a native-language version may be perceived as an expensive luxury). And let&#8217;s not get into the whole P2P thing.<br />
The simple fact that a lot of software used in Europe is actually the US version tilts all sorts of statistics &#8211; including the sort of statistics companies use to justify their international pricing policies. This pushes us into a vicious spiral, one which I think has already started. It&#8217;s up to Adobe to sort it out. By all means charge us Europeans a little more for all the reasons that software companies confronted with this practise fall back on (none of which stand up to close scrutiny). Most of us will give you the benefit of the doubt. There&#8217;ll always be some who buy US versions simply because they&#8217;re a bit cheaper. Adobe need to get their pricing structure organised to the point where, for most of us over here, it makes more sense to &#8216;buy local&#8217;.<br />
If pricing was fairer, it would also take away one of the &#8216;justifications&#8217; used by the P2P brigade. That would lead to less people going down that route. That would mean them actually paying money for their software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://blogs.adobe.com/jnack/2008/08/dear_adobe.html#comment-9013</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 30 Sep 2008 03:58:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/08/dear-adobe.html#comment-9013</guid>
		<description><![CDATA[John
you should probably read this:
&lt;a href=&quot;http://www.theinquirer.net/gb/inquirer/news/2008/09/29/adobe-cs4-pricing-plain-wrong&quot; rel=&quot;nofollow&quot;&gt;http://www.theinquirer.net/gb/inquirer/news/2008/09/29/adobe-cs4-pricing-plain-wrong&lt;/a&gt;
Please get the powers-that-be to pay attention to this, it&#039;s doing nothing good to Adobe&#039;s reputation.
]]></description>
		<content:encoded><![CDATA[<p>John<br />
you should probably read this:<br />
<a href="http://www.theinquirer.net/gb/inquirer/news/2008/09/29/adobe-cs4-pricing-plain-wrong" rel="nofollow">http://www.theinquirer.net/gb/inquirer/news/2008/09/29/adobe-cs4-pricing-plain-wrong</a><br />
Please get the powers-that-be to pay attention to this, it&#8217;s doing nothing good to Adobe&#8217;s reputation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AJ</title>
		<link>http://blogs.adobe.com/jnack/2008/08/dear_adobe.html#comment-9012</link>
		<dc:creator>AJ</dc:creator>
		<pubDate>Sun, 28 Sep 2008 20:21:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/08/dear-adobe.html#comment-9012</guid>
		<description><![CDATA[&lt;i&gt;[You&#039;re mistaken, actually. We put a lot of work into making Photoshop CS3 launch faster and made great progress. I&#039;ve just seen the final results for CS4, and overall running a suite of actions is faster than it was in CS3 on the same hardware. When you factor in the new GPU and 64-bit features in CS4, other wins become apparent. --J.]&lt;/i&gt;
I&#039;m glad to hear it.  But my recent experience with Photoshop, Photoshop Elements, Lightroom, and Reader leaves room for a lot of improvement in this area.  Switching between modules in Lightroom (1.4) is painfully slow, and I can&#039;t even browse my library of images quickly because Lightroom insists on continuously re-generating the thumbnails.  I&#039;ve read that LR 2.0 is even worse in this regard although I haven&#039;t experienced that first hand.
From what you&#039;ve said in your reply it sounds like Adobe is putting more focus on responsiveness over feature capability.  That&#039;s a good thing.  But I suspect that in order for most users to once again feel like Adobe&#039;s products are fast and responsive the balance needs to shift even further.
What is the standard for acceptable speed?  If a function is &quot;acceptable&quot; on the latest and greatest hardware, it&#039;s not going to be acceptable on mid-range equipment, or even on three year old top of the line stuff.  Most of us can&#039;t afford to upgrade our computers annually.
]]></description>
		<content:encoded><![CDATA[<p><i>[You're mistaken, actually. We put a lot of work into making Photoshop CS3 launch faster and made great progress. I've just seen the final results for CS4, and overall running a suite of actions is faster than it was in CS3 on the same hardware. When you factor in the new GPU and 64-bit features in CS4, other wins become apparent. --J.]</i><br />
I&#8217;m glad to hear it.  But my recent experience with Photoshop, Photoshop Elements, Lightroom, and Reader leaves room for a lot of improvement in this area.  Switching between modules in Lightroom (1.4) is painfully slow, and I can&#8217;t even browse my library of images quickly because Lightroom insists on continuously re-generating the thumbnails.  I&#8217;ve read that LR 2.0 is even worse in this regard although I haven&#8217;t experienced that first hand.<br />
From what you&#8217;ve said in your reply it sounds like Adobe is putting more focus on responsiveness over feature capability.  That&#8217;s a good thing.  But I suspect that in order for most users to once again feel like Adobe&#8217;s products are fast and responsive the balance needs to shift even further.<br />
What is the standard for acceptable speed?  If a function is &#8220;acceptable&#8221; on the latest and greatest hardware, it&#8217;s not going to be acceptable on mid-range equipment, or even on three year old top of the line stuff.  Most of us can&#8217;t afford to upgrade our computers annually.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AJ</title>
		<link>http://blogs.adobe.com/jnack/2008/08/dear_adobe.html#comment-9011</link>
		<dc:creator>AJ</dc:creator>
		<pubDate>Sat, 27 Sep 2008 14:48:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/08/dear-adobe.html#comment-9011</guid>
		<description><![CDATA[From a user&#039;s perspective, what I see is this:  Computers have become faster, and your applications have become slower.
&lt;i&gt;[You&#039;re mistaken, actually.  We put a lot of work into making Photoshop CS3 launch faster and made great progress.  I&#039;ve just seen the final results for CS4, and overall running a suite of actions is faster than it was in CS3 on the same hardware.  When you factor in the new GPU and 64-bit features in CS4, other wins become apparent.  --J.]&lt;/i&gt;
That&#039;s the wrong way round.
It doesn&#039;t matter what the reasons.  What does matter is the user experience, and key to that is responsiveness to the user.  Sitting and staring at the monitor while the application loads (and loads and loads) or updates or does who-knows-what when I want to get to work is annoying.  Trying to use a tool and having to deal with lag or repeated appearances of the &quot;wait&quot; icon interrupting the task is unbelievably frustrating.
The user comes first.  If a new application, or feature within an application, cannot be made responsive, fix it, simplify it, or drop it.
&lt;i&gt;[We do that all the time.  Earlier this year we gave a sneak peek of some very cool selection-refining technology we&#039;ve been developing.  When push came to shove, however, it became clear that we weren&#039;t going to be able to make it as fast as it needed to be to ship.  It&#039;ll still be a great feature eventually, but we&#039;re not going to ship it in a state that makes interaction unpleasant.  --J.]&lt;/i&gt;
]]></description>
		<content:encoded><![CDATA[<p>From a user&#8217;s perspective, what I see is this:  Computers have become faster, and your applications have become slower.<br />
<i>[You're mistaken, actually.  We put a lot of work into making Photoshop CS3 launch faster and made great progress.  I've just seen the final results for CS4, and overall running a suite of actions is faster than it was in CS3 on the same hardware.  When you factor in the new GPU and 64-bit features in CS4, other wins become apparent.  --J.]</i><br />
That&#8217;s the wrong way round.<br />
It doesn&#8217;t matter what the reasons.  What does matter is the user experience, and key to that is responsiveness to the user.  Sitting and staring at the monitor while the application loads (and loads and loads) or updates or does who-knows-what when I want to get to work is annoying.  Trying to use a tool and having to deal with lag or repeated appearances of the &#8220;wait&#8221; icon interrupting the task is unbelievably frustrating.<br />
The user comes first.  If a new application, or feature within an application, cannot be made responsive, fix it, simplify it, or drop it.<br />
<i>[We do that all the time.  Earlier this year we gave a sneak peek of some very cool selection-refining technology we've been developing.  When push came to shove, however, it became clear that we weren't going to be able to make it as fast as it needed to be to ship.  It'll still be a great feature eventually, but we're not going to ship it in a state that makes interaction unpleasant.  --J.]</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://blogs.adobe.com/jnack/2008/08/dear_adobe.html#comment-9010</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Fri, 26 Sep 2008 04:29:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/08/dear-adobe.html#comment-9010</guid>
		<description><![CDATA[&quot;You know, Adobe is a big corporation. Maybe John and others aren&#039;t ALLOWED to discuss the pricing situation.&quot;
Yes, I know. I&#039;m calming down about this issue now.
I don&#039;t mind what Adobe are asking for their products. I just object to paying significantly more for the exact same thing than other people do.
And I know that John has tried to get a response to that objection. Adobe&#039;s failure to offer any kind of explanation suggests to me and many, many others that they don&#039;t have one, at least one that&#039;s palatable to their user base outside the USA.
On the plus side, it means I can book a weekend in New York, see a show, buy Design Premium CS4, fly back and be &lt;i&gt;no worse off than buying it online in the UK.
Which is obviously crazy, but there you go.&lt;/i&gt;
]]></description>
		<content:encoded><![CDATA[<p>&#8220;You know, Adobe is a big corporation. Maybe John and others aren&#8217;t ALLOWED to discuss the pricing situation.&#8221;<br />
Yes, I know. I&#8217;m calming down about this issue now.<br />
I don&#8217;t mind what Adobe are asking for their products. I just object to paying significantly more for the exact same thing than other people do.<br />
And I know that John has tried to get a response to that objection. Adobe&#8217;s failure to offer any kind of explanation suggests to me and many, many others that they don&#8217;t have one, at least one that&#8217;s palatable to their user base outside the USA.<br />
On the plus side, it means I can book a weekend in New York, see a show, buy Design Premium CS4, fly back and be <i>no worse off than buying it online in the UK.<br />
Which is obviously crazy, but there you go.</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SteveJ</title>
		<link>http://blogs.adobe.com/jnack/2008/08/dear_adobe.html#comment-9009</link>
		<dc:creator>SteveJ</dc:creator>
		<pubDate>Wed, 24 Sep 2008 10:52:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/08/dear-adobe.html#comment-9009</guid>
		<description><![CDATA[You know, Adobe is a big corporation.  Maybe John and others aren&#039;t ALLOWED to discuss the pricing situation.
&lt;i&gt;[It&#039;s not a matter of being allowed so much as of me not being the right person to do the discussion.  I have no involvement in the development of Adobe&#039;s pricing, so I&#039;d rather you hear info from the horse&#039;s mouth, so to speak.  --J.]&lt;/i&gt;
]]></description>
		<content:encoded><![CDATA[<p>You know, Adobe is a big corporation.  Maybe John and others aren&#8217;t ALLOWED to discuss the pricing situation.<br />
<i>[It's not a matter of being allowed so much as of me not being the right person to do the discussion.  I have no involvement in the development of Adobe's pricing, so I'd rather you hear info from the horse's mouth, so to speak.  --J.]</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://blogs.adobe.com/jnack/2008/08/dear_adobe.html#comment-9008</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 24 Sep 2008 07:48:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/08/dear-adobe.html#comment-9008</guid>
		<description><![CDATA[John
I am disappointed, but not surprised, that no-one from Adobe has answered questions about pricing disparities between different regions.
But I can&#039;t describe how angry I am that Adobe are doing the same thing with CS4: it&#039;s between 50% and 60% more expensive in the UK, and considerably more in the &#039;Euro-zone&#039;.
Are Adobe banking on the fact that many users this side of the pond will have no choice but to stump up? Well, maybe we will. But we will also know that we&#039;re being ripped off, and that&#039;s not good for Adobe or for us.
]]></description>
		<content:encoded><![CDATA[<p>John<br />
I am disappointed, but not surprised, that no-one from Adobe has answered questions about pricing disparities between different regions.<br />
But I can&#8217;t describe how angry I am that Adobe are doing the same thing with CS4: it&#8217;s between 50% and 60% more expensive in the UK, and considerably more in the &#8216;Euro-zone&#8217;.<br />
Are Adobe banking on the fact that many users this side of the pond will have no choice but to stump up? Well, maybe we will. But we will also know that we&#8217;re being ripped off, and that&#8217;s not good for Adobe or for us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://blogs.adobe.com/jnack/2008/08/dear_adobe.html#comment-9007</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Tue, 23 Sep 2008 14:44:53 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/08/dear-adobe.html#comment-9007</guid>
		<description><![CDATA[I have a huge problem with Adobe&#039;s upgrade policy.  When CS3 came out I had just purchased Premiere Pro and Encore and was told I had to pay the same price for an upgrade as someone who had never Paid Adobe for Encore previously.  (I should have recieved more of a discount!)
Now I purchased Photoshop CS3 less than two month ago and Adobe wants me to pay another $199 in order to get CS4?
I think if they keep this up customers will be looking for non-Adobe solutions!
&lt;i&gt;[Why is this related to Adobe in particular?  If you bought a Canon 5D last week, would you expect to get a discount on the 5D Mark II in November?  What if you bought a new computer or car right before a faster, cheaper version was announced?  --J.]&lt;/i&gt;
Grrrrr!!!!!!!  Snarl!!!!!!!
]]></description>
		<content:encoded><![CDATA[<p>I have a huge problem with Adobe&#8217;s upgrade policy.  When CS3 came out I had just purchased Premiere Pro and Encore and was told I had to pay the same price for an upgrade as someone who had never Paid Adobe for Encore previously.  (I should have recieved more of a discount!)<br />
Now I purchased Photoshop CS3 less than two month ago and Adobe wants me to pay another $199 in order to get CS4?<br />
I think if they keep this up customers will be looking for non-Adobe solutions!<br />
<i>[Why is this related to Adobe in particular?  If you bought a Canon 5D last week, would you expect to get a discount on the 5D Mark II in November?  What if you bought a new computer or car right before a faster, cheaper version was announced?  --J.]</i><br />
Grrrrr!!!!!!!  Snarl!!!!!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Davies</title>
		<link>http://blogs.adobe.com/jnack/2008/08/dear_adobe.html#comment-9006</link>
		<dc:creator>Ian Davies</dc:creator>
		<pubDate>Tue, 23 Sep 2008 08:54:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/08/dear-adobe.html#comment-9006</guid>
		<description><![CDATA[Price of &#039;English&#039; CS4 Design Premium from US store - ($1,799)
Price of &#039;Spanish&#039; CS4 Design Premium from US store - ($1,799)
Price of &#039;English&#039; CS4 Design Premium from UK store - ($2,318)
Price of &#039;Spanish&#039; CS4 Design Premium from UK store - ($3,239)
All prices are those listed on the Adobe store, exclusive of any sales tax or delivery and converted using exchange rate at time of writing 1 British Pound = 1.856 US Dollars.
Spanish CS4 is $360 MORE in the UK than CS3.3 was just last week.
Conclusions:
Adobe thinks its customers are stupid.
Adobe deserves to have its marketshare stolen from underneath it by a more reasonably-priced competitor that releases bug-fixes without calling them paid upgrades.
As a direct result of this, I will actively seek out smaller, more focussed, more reasonably priced alternatives to all of Adobe&#039;s applications that I use.
Pushing out over-priced, conveyor-belt &#039;major&#039; versions every 18 months, regardless of whether there&#039;s sufficient new functionality to make it worthwhile is like a geriatric dog that just drops a turd wherever it&#039;s standing.
Better hope you don&#039;t get put down...
Fuck you very much.
]]></description>
		<content:encoded><![CDATA[<p>Price of &#8216;English&#8217; CS4 Design Premium from US store &#8211; ($1,799)<br />
Price of &#8216;Spanish&#8217; CS4 Design Premium from US store &#8211; ($1,799)<br />
Price of &#8216;English&#8217; CS4 Design Premium from UK store &#8211; ($2,318)<br />
Price of &#8216;Spanish&#8217; CS4 Design Premium from UK store &#8211; ($3,239)<br />
All prices are those listed on the Adobe store, exclusive of any sales tax or delivery and converted using exchange rate at time of writing 1 British Pound = 1.856 US Dollars.<br />
Spanish CS4 is $360 MORE in the UK than CS3.3 was just last week.<br />
Conclusions:<br />
Adobe thinks its customers are stupid.<br />
Adobe deserves to have its marketshare stolen from underneath it by a more reasonably-priced competitor that releases bug-fixes without calling them paid upgrades.<br />
As a direct result of this, I will actively seek out smaller, more focussed, more reasonably priced alternatives to all of Adobe&#8217;s applications that I use.<br />
Pushing out over-priced, conveyor-belt &#8216;major&#8217; versions every 18 months, regardless of whether there&#8217;s sufficient new functionality to make it worthwhile is like a geriatric dog that just drops a turd wherever it&#8217;s standing.<br />
Better hope you don&#8217;t get put down&#8230;<br />
Fuck you very much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chad</title>
		<link>http://blogs.adobe.com/jnack/2008/08/dear_adobe.html#comment-9005</link>
		<dc:creator>Chad</dc:creator>
		<pubDate>Mon, 15 Sep 2008 14:32:04 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/08/dear-adobe.html#comment-9005</guid>
		<description><![CDATA[Let&#039;s focus on the principle issues listed in the top 10 gripes at DearAdobe.com.
BLOAT &amp; SPEED:
John said:
[ Will customers actually pay for just polish &amp; bug-fixing? It will be very interesting to see what price Apple asks for Snow Leopard. My suspicion is that to command revenue, you need to deliver both sizzle and steak, changes both big and small. --J.]
Considering that at least three of the current top 10 gripes are about cutting the bloat and making Adobe products faster, I think there are a number of people who truly are serious about this.  Adobe Reader 8 for Mac clocks in at 112MB, whereas Apple&#039;s Preview 4 is 18MB in size.  Unless an Adobe product is absolutely required, I prefer to use more light weight applications (Preview, Acorn) for my work.  So I would say, yes, there actually are some people who would prefer a performance increase instead of a bunch of new features (which they may or may not use).
INSTALLER/UPDATER
The installation and updating process is a devil I&#039;ve had to wrestle many times, especially with CS3.  Did you have the PS CS3 Beta?  Guess what, the final version won&#039;t install without having to do some serious clean up of your system.  The installer works sometimes, and other times it just locks up.  The updater also works... occasionally.  I&#039;ve seen several cases where it refuses to even launch.  Other times it won&#039;t even find the new software.  And if you are hoping that the updater will make it all the way through successfully, one might want to take up religion first.  Installing Adobe Reader 7 was beautiful and simple.  Just drag and drop.  Reader 8 and 9 got ridiculous with their install process.  When people are griping about just trying to install the program, that can&#039;t be a good sign.
PRICING
I&#039;ve heard similar complaints from my British co-workers that Adobe products get REAL expensive outside of the U.S.  Hopefully someone is reevaluating this and making the non-U.S. pricing more reasonable.
]]></description>
		<content:encoded><![CDATA[<p>Let&#8217;s focus on the principle issues listed in the top 10 gripes at DearAdobe.com.<br />
BLOAT &amp; SPEED:<br />
John said:<br />
[ Will customers actually pay for just polish &amp; bug-fixing? It will be very interesting to see what price Apple asks for Snow Leopard. My suspicion is that to command revenue, you need to deliver both sizzle and steak, changes both big and small. --J.]<br />
Considering that at least three of the current top 10 gripes are about cutting the bloat and making Adobe products faster, I think there are a number of people who truly are serious about this.  Adobe Reader 8 for Mac clocks in at 112MB, whereas Apple&#8217;s Preview 4 is 18MB in size.  Unless an Adobe product is absolutely required, I prefer to use more light weight applications (Preview, Acorn) for my work.  So I would say, yes, there actually are some people who would prefer a performance increase instead of a bunch of new features (which they may or may not use).<br />
INSTALLER/UPDATER<br />
The installation and updating process is a devil I&#8217;ve had to wrestle many times, especially with CS3.  Did you have the PS CS3 Beta?  Guess what, the final version won&#8217;t install without having to do some serious clean up of your system.  The installer works sometimes, and other times it just locks up.  The updater also works&#8230; occasionally.  I&#8217;ve seen several cases where it refuses to even launch.  Other times it won&#8217;t even find the new software.  And if you are hoping that the updater will make it all the way through successfully, one might want to take up religion first.  Installing Adobe Reader 7 was beautiful and simple.  Just drag and drop.  Reader 8 and 9 got ridiculous with their install process.  When people are griping about just trying to install the program, that can&#8217;t be a good sign.<br />
PRICING<br />
I&#8217;ve heard similar complaints from my British co-workers that Adobe products get REAL expensive outside of the U.S.  Hopefully someone is reevaluating this and making the non-U.S. pricing more reasonable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://blogs.adobe.com/jnack/2008/08/dear_adobe.html#comment-9004</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Mon, 15 Sep 2008 10:14:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/08/dear-adobe.html#comment-9004</guid>
		<description><![CDATA[&quot;Of course the top engineering item, &#039;Stop creating new features and make your software fast, stable and straightforward,&#039; really means &#039;stop creating new features except for the ones that really help me.&#039;&quot;
*facepalm*  That sounds like an engineering team that just doesn&#039;t get it.  They&#039;re hearing, but they&#039;re not listening.
The last version of Illustrator I bought was Illustrator 10.  If you came to me and offered an Illustrator 10.5 upgrade, and it worked exactly the same as 10.0 but faster and without the bugs, I would have bought it.
No more crashing, no more spinning beachball for 5 minutes (even though I&#039;m editing a small document with 2 gigs of RAM), no more &quot;auto-updates&quot; from the web which destroy my Illustrator.app, an installer that actually works (without forcing me to call tech support and muck around in my System folder first), and so on.  Zero new features.  That would have been the world&#039;s easiest sale, because I know I like Illustrator 10 (and I&#039;ve invested the time to learn it).  I just didn&#039;t like that it was so buggy.
Instead we got &quot;Illustrator CS&quot;.  Funny name (version numbers aren&#039;t good enough any more?), new fluff features (pseudo-3d?), and no claims that any bugs were fixed.  (On Amazon, it has 2.5 stars, and the second review is titled &quot;too darn buggy&quot;.)  I can&#039;t justify spending any money on that.  Today, the Illustrator webpage says &quot;CS3 users are finding a number of new features exciting&quot;.  I guess bugfixes don&#039;t make good ad copy.
I&#039;ve got Illustrator 10 open right now, for a new webpage design I&#039;m working on.
Open-source applications, as awful as they often are, have release notes that are full of &quot;fixed bug #12345&quot;.  I&#039;ve never seen mention of bug fixes in Adobe software releases.  It&#039;s like you refuse to admit that your own software has bugs, much less that us users care about them getting fixed.  And that is often even more frustrating than the bugs themselves.
]]></description>
		<content:encoded><![CDATA[<p>&#8220;Of course the top engineering item, &#8216;Stop creating new features and make your software fast, stable and straightforward,&#8217; really means &#8216;stop creating new features except for the ones that really help me.&#8217;&#8221;<br />
*facepalm*  That sounds like an engineering team that just doesn&#8217;t get it.  They&#8217;re hearing, but they&#8217;re not listening.<br />
The last version of Illustrator I bought was Illustrator 10.  If you came to me and offered an Illustrator 10.5 upgrade, and it worked exactly the same as 10.0 but faster and without the bugs, I would have bought it.<br />
No more crashing, no more spinning beachball for 5 minutes (even though I&#8217;m editing a small document with 2 gigs of RAM), no more &#8220;auto-updates&#8221; from the web which destroy my Illustrator.app, an installer that actually works (without forcing me to call tech support and muck around in my System folder first), and so on.  Zero new features.  That would have been the world&#8217;s easiest sale, because I know I like Illustrator 10 (and I&#8217;ve invested the time to learn it).  I just didn&#8217;t like that it was so buggy.<br />
Instead we got &#8220;Illustrator CS&#8221;.  Funny name (version numbers aren&#8217;t good enough any more?), new fluff features (pseudo-3d?), and no claims that any bugs were fixed.  (On Amazon, it has 2.5 stars, and the second review is titled &#8220;too darn buggy&#8221;.)  I can&#8217;t justify spending any money on that.  Today, the Illustrator webpage says &#8220;CS3 users are finding a number of new features exciting&#8221;.  I guess bugfixes don&#8217;t make good ad copy.<br />
I&#8217;ve got Illustrator 10 open right now, for a new webpage design I&#8217;m working on.<br />
Open-source applications, as awful as they often are, have release notes that are full of &#8220;fixed bug #12345&#8243;.  I&#8217;ve never seen mention of bug fixes in Adobe software releases.  It&#8217;s like you refuse to admit that your own software has bugs, much less that us users care about them getting fixed.  And that is often even more frustrating than the bugs themselves.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
