{"id":16109,"date":"2009-11-23T16:05:16","date_gmt":"2009-11-23T16:05:16","guid":{"rendered":"http:\/\/blogs.adobe.com\/jnackdev\/2009\/11\/photoshop-vs-fireworks-quick-clarifications.html"},"modified":"2009-11-23T16:05:16","modified_gmt":"2009-11-23T16:05:16","slug":"photoshop_vs_fireworks_quick_clarification","status":"publish","type":"post","link":"http:\/\/jnack.com\/blog\/2009\/11\/23\/photoshop_vs_fireworks_quick_clarification\/","title":{"rendered":"Photoshop &quot;vs.&quot; Fireworks: Quick clarifications"},"content":{"rendered":"<p>Thanks for <a href=\"http:\/\/blogs.adobe.com\/jnack\/2009\/11\/feedback_please_graphic_web_design_enhancements_in_ps.html#comments\">all the feedback<\/a> in response to the <a href=\"http:\/\/www.surveymonkey.com\/s.aspx?sm=Cc9ZzCqEB0FoUWjAZ2qUwQ_3d_3d\">survey<\/a> I posted earlier today.  I feel I should clarify a few things.<\/p>\n<ul>\n<\/p>\n<li>I&#8217;m touchy about hearing things like &#8220;As soon as Adobe bought Fireworks, the PS guys would be trying to kill it. Good job, mission accomplished.&#8221;  To set the record straight, Adobe bought and <em>revived<\/em> Fireworks.  To the best of my knowledge the app hadn&#8217;t gotten much love, to say the least, in its last couple of years with Macromedia.  (Did they add <em>anything<\/em> in Studio 8?)  And when Adobe was in the process of acquiring Macromedia, I spoke up strongly in support of Fireworks.  Just thought you should know.<\/li>\n<p><\/p>\n<li>The list I posted isn&#8217;t a promise or a hint that the Photoshop team will undertake <em>any<\/em>&#8211;much less all&#8211;of this work.  As I say, it&#8217;s just my aggregation of some of the suggestions I&#8217;ve heard a number of times.  I thought it would be handy to collect them for your input.<\/li>\n<p><\/p>\n<li>Likewise, it isn&#8217;t a hint about the future of Fireworks or anything else.  Sometimes a survey is just a survey.<\/li>\n<p><\/p>\n<li>Believe me, we&#8217;re <a href=\"http:\/\/blogs.adobe.com\/jnack\/2005\/10\/psst--wanna_see.html\">sensitive<\/a> to the subject of &#8220;<a href=\"http:\/\/blogs.adobe.com\/jnack\/2006\/05\/get_lean_stay_hungry.html\">bloat<\/a>,&#8221; and I&#8217;m actively pitching ideas (<a href=\"http:\/\/www.jnack.com\/adobe\/photoshop\/obo\/1.html\">here&#8217;s one<\/a>) for how the apps can better integrate without just duplicating one another.  Having said that, we can&#8217;t err too far in the other direction, saying that if one app does something, no others can do it (or do it well).  It&#8217;s possible for apps to have different core missions and yet have tools &amp; capabilities in common.  (To that end, people flamed us for not moving animated GIF import from ImageReady to Photoshop, feeling it was a conspiracy to force them to buy Fireworks.  Damned if you do, damned if you don&#8217;t.)<\/li>\n<p><\/p>\n<li>People have <em>always<\/em> complained that Photoshop does too many things.  I guarantee that whoever added text for the first time got an earful about it not being a &#8220;photographic&#8221; feature, and probably caught static from other Adobe teams.  So it goes.  Of course, people always say, &#8220;Stop adding anything new&#8230; <em>except this handful of things for me, personally.&#8221;<\/em>  And they always push us to &#8220;simplify&#8221; and &#8220;just reduce&#8221; the application, yet they flip out if you take away their cherished anachronism.  I always think of the Onion article, &#8220;<a href=\"http:\/\/www.theonion.com\/content\/news\/report_98_percent_of_u_s_commuters\">98 Percent Of U.S. Commuters Favor Public Transportation For Others<\/a>.&#8221;<\/li>\n<p><\/p>\n<li>We have <a href=\"http:\/\/blogs.adobe.com\/jnack\/2009\/08\/feedback_please_task-based_workspaces_in_ps.html\">serious ideas<\/a> about how to break this logjam, but there are no silver bullets, and it&#8217;s not going to happen overnight.  But it is happening.<\/li>\n<p><\/p>\n<li>Finally, a couple of practical tips: Here&#8217;s a <a href=\"http:\/\/www.adobe.com\/cfusion\/exchange\/index.cfm?event=extensionDetail&amp;loc=en_us&amp;extid=1516518\">Lorem Ipsum generator for PS<\/a>, and here&#8217;s the <a href=\"http:\/\/blogs.adobe.com\/jnack\/2009\/02\/gridmaker_panel.html\">GridMaker panel<\/a>.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Thanks for all the feedback in response to the survey I posted earlier today. I feel I should clarify a few things. I&#8217;m touchy about hearing things like &#8220;As soon as Adobe bought Fireworks, the PS guys would be trying to kill it. Good job, mission accomplished.&#8221; To set the record straight, Adobe bought and [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts\/16109"}],"collection":[{"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/comments?post=16109"}],"version-history":[{"count":0,"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts\/16109\/revisions"}],"wp:attachment":[{"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/media?parent=16109"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/categories?post=16109"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/tags?post=16109"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}