P: Transform/Resize is constrained by default - Want ability to go back to legacy behavior

If it takes jeffrey two hrs to do something that used to take 20 mins hes on salary, whats not done today will do tomorrow but the salary is the same.

Jeffrey is a salaried employee of Adobe, with pension and benefits paid with our subscriptions... where do you think his loyalty lies?
Why would he stick his neck out for us and jeopardise his pension?

I dont care if they change something really — but I agree and think that what most people are asking for is a simple way to choose — perhaps a setting in Preferences, duh — that would allow us to choose the legacy behavior of using the SHIFT key or not.

What I cant support is them telling us that there is a sh&tty workaround — we have to fire up a text editor and write a config file and move it to a location deep within the system folder hierarchy? Seriously, now I am editing software? That is what I pay them for!

If they simply put it as a checkbox in Preferences in the next release this entire conversation would be over.

— 
BTW who is Jeffery? Why should we believe him?

On Twitter

Terry White
@terrylwhite

Scott Kelby
@ScottKelby

I posted a link to one of the better comments from here on Twitter this morning and a rep responded immediately. It was an insufficient response but a response nonetheless.

The rep was completely out of touch with reality and lacked a general knowledge of  UX principles.

Here is a link to it:
https://twitter.com/AdobeCare/status/1103371716955385856

Totally agree — anywhere but on here. Or more to the point, everywhere and on here.

But if we only post on here they are going to ignore us.

Me too. But i think that is a ruse to get us OFF Twitter. They cant control the story on Twitter like they can here — or rather flat out ignore it like they do here.

I've found that every time I've commented about an  PS, LR or Bridge issue on Twitter I've been told by Adobe people to post to this forum. It's just a way to kick the can.

It would be amazing if we could see more parity across Adobe applications

That was one of the stated goals of the original CS suite, we've been waiting a LONG TIME for that! Some things have improved but the differences in the way apps accomplish the same tasks is huge.

Could you imagine the uproar if the behaviour of the Shift key changed in Illustrator and InDesign and After Effects like it did in Photoshop?

If you identify the 100s of places it needs changing, then actually change it in those places, then announce it and explain why and give people time (you know, roll it out properly) then you'd get a lot of grumbling, which passes.

But this is half-baked and creates anger-inducing inconstancies for pros because we spend our lives avoiding the same mistakes in behalf of our clients. At least take pride in knowing you did it right. I can't imagine breaking something so fundamental to a client's website or app, then fumbling the fall out. I'm sure you couldn't either - right?

 The transform issue has been acknowledged...

Let's be frank, it's was acknowledged about as well as it was announced! Hence "...no real acknowledgement". Somewhere on this 'Get Satisfaction' website, an Adobe employee said the change came about because some users were used to resizing windows in the same way - what does that even mean?

 ...and there are a few workarounds (none of them ideal)

First thing I did so I don't have to worry about this change (for now). But I do worry about what this change says about Adobe - what is going on over there? 

Social Media, their websites, ...
I would suggest starting with social media, and go from there. There are other forums who have posts regarding this insanely stupid change. There's one on Reddit...etc.