Adobe to launch Creative Suite 5 on April 12

Adobe CS5 - First look April 12Adobe today officially announced the launch of Adobe Creative Suite 5 (CS5) will happen on April 12th, 2010.

Those interested can register to join Adobe online for the “exclusive launch of Adobe Creative Suite 5” on Monday, April 12 at 8am PDT / 11am EDT / 5pm CEST.

The company released no further details about the suite of applications, although it’s widely expected that Photoshop CS5 for Mac OS X, at least, will finally make the leap to 64-bit code.

Registration link here.

38 Comments

  1. Adobe could update Creative Suite much less often and I’d be much happier.

    Of course, while I use Photoshop, InDesign, and Dreamweaver CS4 I still use Illustrator CS3 because the Illustrator team is simply incompetent. Each new revision means a new bunch of broken stuff. No thanks.

  2. @Tommy Boy

    I use Illustrator CS4 and haven’t noticed any broken commands or anything compared to CS3. I’m not doubting you; in fact, I’d love to know what they are so I can be aware of them for any future projects. : )

  3. Why can’t Illustrator have the same methods for changing fonts and creating new swatches that Indesign has? It totally sucks to find/change fonts in Illustrator. You would think they would make these things universal in their apps.

  4. Still on CS2 for everything but Dreamweaver, which is CS3. It all flies on my MacBook Pro and still works reasonably well on my G5 iMac. I have no need or desire for all of the Bridge/Version Cue/Flex/Air/Integration/Blah Blah Blah background noise–just give me fast tools that do the jobs I need and don’t get in my way. (I do wish I could hack Dreamweaver CS3’s html rendering so I could do CSS3 stuff and see what it looks like in the program, though. But I’m playing around with Panic’s excellent Coda program as well, which renders pages with OS X’s built-in WebKit.)

  5. @Tommy Boy — that’s good to know. I don’t use text objects much, but I can see how that would be a bother. A REAL bother. Yuck. Well, let’s see if CS5 takes care of that one.

  6. Illustrator?
    Resurrect Freehand!

    Let’s hope that they fix PDF printing in Acrobat Pro under Snow Leopard!

    I believe Adobe is finally ending PowerPC support with CS5, so that should at least make all the apps a bit leaner.

    I skipped CS4, so I’m ready for an upgrade!

  7. Adobe should pull a Snow Leopard and use a whole development cycle to fix their shit.

    Great apps, but they’ve turned into buggy spaghetti over the years.

    I’d pay to have CS3 done right, instead of CS5.

  8. “running CS2 and will finally upgrade to CS5…ONLY reason is to maintain my license since you have to keep up to date every third version or loose the ability to get upgrade pricing.”

    That’s good to know; thanks! Still don’t know if I could stand to upgrade anytime soon, though. Maybe I’ll wait until CS5.9…

  9. We only just finally updated all our seats to CS4.. in fact I installed it only last week. It was necessary as After Effects CS3 has a huge memory leak bug on OSX 10.6.x.

    Now they come and announce CS5? From what I have heard After Effects will, in this iteration be fully 64bit. If this is so, then it will be on the wish list for sure.

    I only hope they don’t try to make us pay full upgrade prices on seats that are only a couple of weeks old… Though I can’t say that I have much faith in the benevolence of Adobe’s pricing policy-setters. Hell, with CS4 even though you plunk down $1700, they still won’t send you physical discs unless you plunk down another $20 (?!?!?)

    Frustrating…

  10. @Randomizer

    “Open Question:
    When is the last time that you were “really excited” about an impending Adobe release?”

    InDesign 1.0 – Couldn’t wait to get my users off Quark Xpress! ” width=”19″ height=”19″ alt=”grin” style=”border:0;” />

  11. CS4 is compilation of 15 applications and each has a different user interface. The real trouble is, these interfaces look identical but behave differently in many areas.

    Going from Photoshop to Illustrator to me is a real let down, because many of the refinements to their flagship product’s interface have failed to materialize in Illustrator, even though Illustrator has been around years longer.

    After all these years, I still can’t scrub-to-change the variables, inside Illustrator’s palettes, like I can with Photoshop. Like scrubbing to increase/decrease the font size, for example. WTF Adobe? Illustrator has always been the superior choice for typography and yet Photoshop’s text palette is “smarter”.

    Another example is Fluid Canvas Rotation, which to me is the single greatest achievement in Photoshop, ever! By pressing the “r” key, I can now rotate the canvas around the z-axis and thanks to OpenGL I can rotate a 100-MB image around and around smoothly as butter. But, not in Illustrator! WTF Adobe? Don’t these individual application developers share trade secrets, or is there some kind of intra-company competition going on?

    Adobe’s suite needs to pivot around a single application designed with workspaces in mind. I’ve always thought Bridge should fill that need. I should be able to choose from a list, the kinds of work I want to do and the Bridge interface would adjust accordingly, much like Photoshop does now, using Workspaces.

    With a single, unified interface that acts as a “Bridge” across the Suite’s entire spectrum of capabilities, Adobe could eventually standardize the capabilities of the entire suite into a single entity, whereby you pay to unlock workspace resources instead paying for individual applications, which in some respects are are like jacks-of-all-trades-and-masters-of-nothing.

    As it stands, each of these programs has, over the years, encroached on one another. Which looks to me as though the developers are a big group of individual teams working at cross-purposes with one another, not unlike the Suite itself. WTF Adobe? Think iLife, libraries, and media shares.

    Adobe, the company, and their Suite are synonymous, a collection of disparate groups unified by a mish-mash interface.

    Get it Together, Adobe™

  12. ALL Macs sold as of August 2006 have been 64-bit capable.

    That means Adobe is over 3.5 years BEHIND Apple in going 64-bit. Great job Adobe.
    ” width=”19″ height=”19″ alt=”tongue laugh” style=”border:0;” />

    This sort of BS is typical of companies with monopoly status. Adobe are also well known to have a contentious work culture. When I saw Adobe listed in the Fortune 100 Best Places To Work for 2009 I just laughed. Maybe it’s a great place to work for lazy coders who don’t care about keeping up with the rest of the computer community.

  13. I know everybody hates Flash all of a sudden but the fact that Flash CS5 will export Flash into iphone pad or pod (ipa) format is huge. No need to learn how to remake it Apple language. So yes I am somewhat “really excited”.

  14. @Flasher

    “somewhat “really excited”

    Really? Is that like, a little bit “pregnant”?

    Ask ten people, and get ten different reasons why they hate Flash, and they all got it somewhere else.

    I’ve never really hated Flash, just the those who don’t know how to use it.

    This website was the straw that broke the camel’s back.

    Be sure to fire up Activity Monitor before you go, so that you can watch your CPU usage peg the needle. His website is the reason I now use Click-to-Flash.

  15. A friend pointed me to Adobe’s Flash blog. The defensive tone it strikes, knocking hither and yon all foes of Flash it utterly ridiculous. The best part is when Adobe attempt to deride their reputation as arrogant, after which they arrogantly dismiss an entirely valid description of exactly how Flash can devour a computer’s CPU when a page with a Flash movie is just sitting there, NOT playing. Adobe’s defense was to tell the nasty customer to install the latest version of the Flash plug-in. How sad that I can perfectly reproduce that nasty customer’s situation WITH the latest version of the Adobe Flash plug-in.

    Adobe are both clueless AND arrogant about their lousy Flash format. They are also entirely unwilling to investigate the fact that CPU-devouring-syndrome occurs in specific situations with specific pages. It is NOT simply a problem of the Flash Plug-in. As G4Dualie indicated above, there are some HORRIBLE Flash movies strewn across the net the for gawd-knows what reason eat your CPU by simply existing. (o_0)

    The real problem? I am willing to bet that Adobe have NO comprehension of the code used in Flash. Why? Adobe BOUGHT Flash when they bought Macromedia. Adobe didn’t code it themselves and they’re either incapable or too lazy to go back and repair the bad original coding. Thusly, I fully expect Flash to always be a big PITA and for Adobe to be always defensively dismissive of the blatantly obvious problems.

    Solution: Move to better alternatives. Dump Flash.

  16. @Derek Currie,

    Don’t forget that even Macromedia BOUGHT Flash from a company who BOUGHT it from someone else. It’s changed a great deal, but like many gigantic apps (I’m looking at you Photoshop and Quark) it’s so complex to change them after all these years that real change to the core is nearly impossible. Some background on Flash, and a list of criticisms, here:

    http://en.wikipedia.org/wiki/Adobe_Flash

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.