"Photoshop CC (2014)"

[digitaldog]

With the existence of these major builds (CC 2014), I don't understand anymore the initial technical rationale explaining why CS7 could not have been released with a perpetual license in parallel with the new subscription model.

Was there ever a technical rationale explaining why CS7 could not have been released with a perpetual license?

[BernardLanguillier]

Was there ever a technical rationale explaining why CS7 could not have been released with a perpetual license?

According to Jeff, yes.

This was his main argument to sell the proposal that Adobe was not just a greedy monopolistic corporation looking for a way to extract even more cash from its faithful customer base to please some MBA fed board members expecting even more return on their investement.

Cheers,
Bernard

[Isaac]

…to please some MBA fed board members…

Fiduciary duties to shareholders.

[chez]

I could see a big reduction in support issues by having everyone on the same revision of software. The CC model basically guarantees this by continually upgrading each CC out there to the latest greatest. With perpetual models, there were many different releases of PS active at once, providing much more stress on support.

I run a product that has many different versions active and trying to provide support for all these different versions taxes out our customer support group.

According to Jeff, yes.

This was his main argument to sell the proposal that Adobe was not just a greedy monopolistic corporation looking for a way to extract even more cash from its faithful customer base to please some MBA fed board members expecting even more return on their investement.

Cheers,
Bernard

[Colorwave]

I could see a big reduction in support issues by having everyone on the same revision of software.

Except this is the opposite of what they just did with this new release. Now we have vanilla Photoshop CC and Photoshop CC 2014.  For me to use the new features rolled out today, I will be running 2014.  For my day to day workflow, though, I will have to revert to the previous CC, so that I can use the custom panels I built, and the third party extensions that no longer work with the newest API that is no longer compatible with Flash extensions or Configurator panels.  As best I can tell, none of the third party extension vendors were ready at launch.

[Jim Kasson]

I'm not seeing the option to upgrade to Ps 2014. The only (2014) app I see is InCopy CC (2014), which I'm not using. I'm on Win 7 x64. Is anyone else not seeing the upgrade in Adobe CC updater app?

Jim

[chez]

Yeh, I don't know why they did that...maybe they knew some people like you would need access to the previous version...but I know one of the goals of moving to the CC model was to get everyone onto the same releases to reduce support costs. Remember Adobe has a huge number of applications, not just PS and supporting all the different versions out there must be a nightmare.

Except this is the opposite of what they just did with this new release. Now we have vanilla Photoshop CC and Photoshop CC 2014.  For me to use the new features rolled out today, I will be running 2014.  For my day to day workflow, though, I will have to revert to the previous CC, so that I can use the custom panels I built, and the third party extensions that no longer work with the newest API that is no longer compatible with Flash extensions or Configurator panels.  As best I can tell, none of the third party extension vendors were ready at launch.

[Schewe]

I hope Jeff or Eric or someone will help us understand what's up with two versions of PS CC eating up valuable SSD space.

So far, all of the previous versions of Photoshop CC were "updates" that patched the core application to add new code. Photoshop CC (2014) is an "upgrade" that needs to have the entire new application downloaded because the new features and functions were beyond the scope of a code patch...note the (2014) meaning this is the first major upgrade...additional "updates" will patch the current new code.

In the future (prolly 2015) there will be another "upgrade" which will again require downloading and installing the whole app.

[Schewe]

This was his main argument to sell the proposal that Adobe was not just a greedy monopolistic corporation looking for a way to extract even more cash from its faithful customer base to please some MBA fed board members expecting even more return on their investement.

Yeah, ya know...I'm not going down that road again...everything I said was true then (as it is now). What you want to make of it is your own business...

Note, the upgrade to Photoshop CC (2014) is free to subscribers...so, I really don't understand how you can spin that into a greedy Adobe argument.

[BernardLanguillier]

Yeah, ya know...I'm not going down that road again...everything I said was true then (as it is now). What you want to make of it is your own business...

Note, the upgrade to Photoshop CC (2014) is free to subscribers...so, I really don't understand how you can spin that into a greedy Adobe argument.

Jeff,

Free to subscribers is an interesting way to put it.

But you are correct that CC 2014 doesn't add, or substract, anything to/from the original greediness I believed motivated the move to a subscription only model.

Cheers,
Bernard

[Schewe]

Free to subscribers is an interesting way to put it.

So...Photoshop CC (2014) did not cost CC subscribers any additional fee for upgrading...so, it was a free (no cost included) upgrade. So, I'm wrong that I called it a free upgrade?

If you are spoiling for a fight, I decline...as I said, I'm not going down that road again. A whole lot of people reacted irrationally to the changes Adobe enforced. That's on them (and you). I gave up caring about what they (you) think...

If you want facts and/or knowledge, I'll give it–if you want to rant and rage, screw you...and yes, the Photoshop CC (2014) full app upgrade actually enforces my statement that dual code bases resulted in Adobe dropping CS7...the original CC app needed to have a whole new code branch, hence the new CC (2014) code base. There's only so much Adobe can do with code before a new app code needs to be spawned. If you understood software development, you would understand this.

[Geraldo Garcia]

The way I see it Adobe was very prudent. As the new version didn't hold full compatibility to previous extensions (the cost of moving forward and making some improvements) they had the decency of launching it as a separate version, so we can have both at the same time until plug-ins and extensions are updated. That is a good thing. Yeah, "cc 2014" is kind of lame when you think about the concept they advertised of "the definitive and ever-changing Photoshop", but I think it was necessary for our own good.     

[Colorwave]

Jeff, other than the new features I have read about, were there significant changes to the code base, aside from dropping Flash support from within the API itself?  I'm just curious.

[Schewe]

Jeff, other than the new features I have read about, were there significant changes to the code base, aside from dropping Flash support from within the API itself?  I'm just curious.

Well, I can't say other than to say that the totality of the changes required a new app installation vs a code update via a patcher...and yes, rather than overwriting the older CC code it installed a new app partially due to backwards compatibility. It allows one to have both versions and decide on their own, which version to use.

[Colorwave]

Interesting.  I was assuming that it was more about looking ahead, rather than anything that was needed for the new features just released.  

[fdisilvestro]

Hi,

One thing that I noticed is that there is no longer a 32 bit version for CC (2014) so if you have any special plugin that works only on 32 bits, then you might want to keep the old CC version for some time (I can't think of other reason unless you're still using a 32 bit OS)

Regards,

[Martin Kristiansen]

Hey hey a new Photoshop. I am well excited. But then I used to get excited about a new enlarger in the old days. This feels a bit like that but it's free.

[Jim-St]

How can one establish which plugins will simply work by copy & paste from PSCC Plugins folder to PSCC(2014) Plugins folder? And which will fail or cause problems?

We could do with something comparable to what roaringapps.com does for OSX upgrades, listing what will work and what won't, but maybe that's not feasible

For starters, anyone know if PKS2 will work if I copy & paste the PG Toolbox Plugin Module folder into the new version's Plugins folder?

Jim

[Simon J.A. Simpson]

So, we’ve spent some time in this thread trying to deconstruct and understand Adobe’s latest software updates.

Would it not help everyone if Adobe were just clearer on this from the outset ?  Wouldn't it be better just tell us what they are doing instead of leaving it for us to figure out ?

This thread has helped me understand some of what is going on with these software updates but I still don't understand why I am being offered another version of Lightroom (see this thread New Photoshop CC and Lightroom .  Clicking on the link “What’s new” in the Creative Cloud window takes me to a web page talking about Lightroom June 2013.  Thus, my confusion.  It could mean that I will get Lightroom 5.5 but that the software update panel is giving me misleading information ?  Or it could mean I get a new version of Lightroom ?  Would be good to know.

(sound of distant gunfire – see New Photoshop CC and Lightroom )

[digitaldog]

For starters, anyone know if PKS2 will work if I copy & paste the PG Toolbox Plugin Module folder into the new version's Plugins folder?

Assuming the latest versions, that worked just fine for me under Mac OS X.