will react negatively to any change that requires a little adjustment to workflow or muscle memory, or even if things just look different.
I wonder if it’s possible to build seperate UI that sits on top of the underlying backend and can be switched easily. So that ppl from PS can start quick.
I think a lot of people underestimate the maintenance burden of options like this. It’s another trope you see often with UI changes – “just let me switch it back.”
The problem is that now, even if your UI is super nicely decoupled from your engine, everything you change under the hood is likely to need at least regression testing in two places rather than one – that workload has doubled.
As it happens, though, with your specific example, there’s someone actively maintaining a GIMP fork mod called PhotoGIMP to achieve this, but I notice despite recent(ish) commits, they’re still a minor version and a year behind.
I wonder if it’s possible to build seperate UI that sits on top of the underlying backend and can be switched easily. So that ppl from PS can start quick.
I think a lot of people underestimate the maintenance burden of options like this. It’s another trope you see often with UI changes – “just let me switch it back.”
The problem is that now, even if your UI is super nicely decoupled from your engine, everything you change under the hood is likely to need at least regression testing in two places rather than one – that workload has doubled.
As it happens, though, with your specific example, there’s someone actively maintaining a GIMP
forkmod called PhotoGIMP to achieve this, but I notice despite recent(ish) commits, they’re still a minor version and a year behind.The whole conversation reminds me of this XKCD
you just explained fairly well to me why windows decided to lock the taskbar on the bottom for a while. or at least a reason they might.
Like with Linux distros and which DE you run?
there have been several, including one that tried to look like photoshop but then ended up being malware.