5 ms·

In Photoshop there are at least three completely different dialog boxes [0] for saving an image as a JPEG, each with totally different UI widgets and functional

In Photoshop there are at least three completely different dialog boxes [0] for saving an image as a JPEG, each with totally different UI widgets and functionality. They simply refuse to revise anything in the interface—they just keep adding. It's the software equivalent of hoarding. [0] Save/Save as, Export As, Save for Web (Legacy)

bombcar 2y ago
I'm ride-or-die on Save for Web (Legacy), it's the way to go by far. Now if they'd just integrate the tinypng plugin that was deprecated in 2023 - https://help.tinify.com/help/deprecation-of-the-photoshop-plugin https://help.tinify.com/help/deprecation-of-the-photoshop-pl...
- turnsout 2y ago
  Same—I just wish they'd either drop the "(Legacy)" and admit that they can never remove it, or add those same features to the Export dialog!
reddalo 2y ago
How long has the Save for Web been "Legacy"? I feel like it's been there for a long time.
- jaredwy 2y ago
  I was the engineer that added that string. Since adding that string... I joined the photoshop team officially. Spent maybe 5 years there. I have left adobe. I Had a year and a half sabbatical. Now writing this comment. It's been a while.
  - turnsout 2y ago
    Ha, comments like this are why I love hn!
- MontagFTB 2y ago
  The intent was to direct customers to the new “Export As” experience, which was a newer code base and handled some things SFW did not. Enough people couldn’t leave SFW behind though, and it’s been Legacy ever since. Anecdotally, SFW is the result of converting Adobe ImageReady into a plugin. When IR was originally created, many of its sources were split off from Photoshop to get it off the ground. So now we have two variants of “the same” sources for many files- one evolving in Photoshop, and the other frozen in time in Save for Web.
grishka 2y ago
There's also two implementations of the "new document" dialog. The old one, that works instantly, and the new one, that takes a solid second to render no matter how fast your machine is. There's a checkbox in settings to use the old one.

bombcar 2y ago

I'm ride-or-die on Save for Web (Legacy), it's the way to go by far. Now if they'd just integrate the tinypng plugin that was deprecated in 2023 - https://help.tinify.com/help/deprecation-of-the-photoshop-plugin https://help.tinify.com/help/deprecation-of-the-photoshop-pl...

turnsout 2y ago
Same—I just wish they'd either drop the "(Legacy)" and admit that they can never remove it, or add those same features to the Export dialog!

reddalo 2y ago

How long has the Save for Web been "Legacy"? I feel like it's been there for a long time.

jaredwy 2y ago
I was the engineer that added that string. Since adding that string... I joined the photoshop team officially. Spent maybe 5 years there. I have left adobe. I Had a year and a half sabbatical. Now writing this comment. It's been a while.
- turnsout 2y ago
  Ha, comments like this are why I love hn!
MontagFTB 2y ago
The intent was to direct customers to the new “Export As” experience, which was a newer code base and handled some things SFW did not. Enough people couldn’t leave SFW behind though, and it’s been Legacy ever since. Anecdotally, SFW is the result of converting Adobe ImageReady into a plugin. When IR was originally created, many of its sources were split off from Photoshop to get it off the ground. So now we have two variants of “the same” sources for many files- one evolving in Photoshop, and the other frozen in time in Save for Web.

grishka 2y ago

There's also two implementations of the "new document" dialog. The old one, that works instantly, and the new one, that takes a solid second to render no matter how fast your machine is. There's a checkbox in settings to use the old one.