

This can sometimes come at the cost of intuitiveness however. As an example that just happened to me the other day, I was using Pinta which uses libadwaita and had opened an image to make some modifications to it.
All was going well until I wanted to save a new copy of it (and not override the original). The toolbar has all of these functions on it, open, save, undo/redo, etc… but not Save As.
Apparently there’s a tiny little overflow button on the far right side, click it and you get a whole bunch of functions - one of them being the holy “Save As” option I was looking for. I almost went down the route of making a copy of the image outside Pinta and then just overwriting the original.
Apparently the idea of making a copy of an image is blasphemy. Even Microsoft Word when they had first moved to the Ribbon UI made the save button have a little dropdown right under the save option to reveal Save As.
Don’t get me wrong, I love how some libadwaita apps look. Mission Center for example? Chef’s Kiss - but it’s a very simple application that all I need to do is open it to have a quick look at the very pretty looking graphs. Although the latest update seems to have gotten rid of being able to have the sidebar open persistently (now taking an extra click to change between performance graphs)… But I still need to double check to see if that’s intended vs being a bug before I judge that too harshly.
How is that the case? I’ve got pretty much zero experience with decompiling software, but I can’t say I’ve ever heard anyone who does say that before. I genuinely can’t imagine that it’s easier to work with say, decompiling a game to make changes to it rather than just having the source available for it.
I suppose unless the context is just regarding running software then of course it’s easier to just run a binary that’s already a binary - but then I’m not sure I see where decompiling comes into relevance.