P: Revert UI to older Camera Raw UI (12.2.1) after Interface Changes

Bridge 12 runs fine on the M1, Bridge 13 is Apple Silicon-native but has a lot of bugs so I don't use it. As for the UI, that's all subjective. I'm a working pro who makes a living with a camera, and I don't think the current Camera RAW UI is a problem. Being non-scriptable is more of an issue for me as I rely heavily on scripts I write to extend Bridge and Photoshop.

@charlesb12994120 I have been running ACR 12.1.1 on an M1 Mini. It works. I am still running old versions of Bridge 10.0.4.157 and Photoshop 21.1.3. I have not updated them to not break anyting. I mostly rely on Bridge and ACR. Bridge is a hot mess. The Content window preview images are scrambled GPU nonsense. As far as I can tell from these boards this issue with Bridge hasn't been resovled in more than 2 years now even with the udated versions. People just have to "live" with it. The Preview window images are fine so it is not a total bust.

To open images directly into ACR you have to do left click and choose open in ACR. A double clip opens ACR and Photoshop. I have not moved past Big Sur either. One simple solution is to have a dedicated old machine i.e. Intel running ACR 12.1.1 for Pro editing use. Since ACR 12,1.1 will allows run in Roseta2 emulation on M1 you get better performance on Intel.

Adobe could have an ACR Pro option in the payment plans for Pro users to access a professional GUI instead of the UIX ACR is now. When you look at the Lightroom UIX ACR next to the GUI of ACR 12.1.1 one looks like you are about to buy something off the internet and the other looks like you are about to edit image files.

I would like to suggest a totally new and shiny cropping option for cropping images in ACR that works just like the legacy mode in Photoshop, (and ACR pre version 13)  

Basically it keeps the image still while you crop, like you would if you were cropping an image in real life.

Developing software is and can be tedious, fix one thing, break another is very common. 

HOWEVER, having software designers and developers driven by marketing rather than users can come up with some pretty f'd up programs. 
For example, in most MS programs F1 brings up help, but if you're a mouse clicker, you go to Help on the toolbar, then have to click Help again because some designer/marketing/project manager decided they should overload Help with other things like contact support, feedback, show training, and what's new. Terrible user experience. 

So maybe Adobe needs to be more transparent about how decisions like this camera raw UI came about. 

On the plus side, this crapy UI experience has forced me to get more into shortcut keys (like for syncing changes in images...) for things no longer obvious on the UI. 

Buddy, you are looking at the 2nd GUI they wasted the time on-- and it blows!!  Put the new features in the old GUI.  

I use these tools to make a living, and the new version slows me down tremendously, if I were forced to use it I would be losing money.  As soon as I find a viable alternative I'm out of here.

As soon indeed.

I am quite certain I am not the first person to tell you that you are not getting what you want. Sorry. 

Buddy, you are looking at the 2nd GUI they wasted the time on-- and it blows!!  Put the new features in the old GUI.  

I use these tools to make a living, and the new version slows me down tremendously, if I were forced to use it I would be losing money.  As soon as I find a viable alternative I'm out of here.

"If this was implemented it would not negatively impact you but would benefit a LOT of others. Just read through the thread if you are not convinced."

Actually, it could and hugely. But then it helps to have actual working experience developing and supporting software. Implementation takes time, costs money, needs alpha and beta testing and documentation, and removes resources for functionality that will aid a larger user group. Look at the new masking features provided since this original request. You may feel that the Adobe team should have put that on the sidelines to add a 2nd GUI you prefer. They thankfully did not. Nor is it likely, after all these years, they will. They have bigger and more important fish to fry (and yes, I and a few others here have some inside info about that that will be). 

There seems to be strong opinions about how software should be developed by people (AFAIK) without experience developing software. 

But look at the facts and feedback. The request was made over 2 years ago. As of just now, there are 5.6K views, 599 replies and 79 votes. With such facts, it would be rather absurd for Adobe to consider this a viable request. You say this will benefit a LOT of others; where are they, and can you get them all here to vote? 

All developers have limited resources and can't make everyone happy. As for the current UI, I'm fine with it. I'd like to see Adobe fix a LOT of other things and not waste any more time on this. SO, no, it wouldn't benefit me.