Also gets into the idea of personalized UI more generally. You can imagine something like Photoshop ought to adapt what tools it shows based on how someone uses it. Then again, that would make learning/teaching and sharing really difficult.
Also gets into the idea of personalized UI more generally. You can imagine something like Photoshop ought to adapt what tools it shows based on how someone uses it. Then again, that would make learning/teaching and sharing really difficult.
I also see another problem: lock-in and loss of productivity in other environments. For this reason I prefer to stick to everything as vanilla as possible: so that I can use another computer or keyboard and it "just works" because that's what I'm used to anyway.
Does it make them more productive? I honestly have my doubts. The number of times I've had to wait during a group project because a software update broke their keybinds, they're at another desk and are now slow because they don't have the muscle memory for 'standard' layouts, etc is not even close to zero. Even on their own systems, they spend significant time every week tweaking things. For many, I think it is a form of bikeshedding as much as anything.
Strong disagree on the second: Photoshop should absolutely not move controls around on some kind of magic guesswork basis. That would destroy visual/muscle memory and undermine the users sense of control and mastery. Bad news.
It would be pretty great if programs with tool palettes came with a configurator so that the user could deliberately move things around, remove and add tools, and otherwise customize. As long as it was saved in a plain-text config that they could move around, this would be a win, just like it is in text editors.
Pretty soon, your emacs is basically incompatible with everyone else's and your carrying around a 2k line .emacs file. Brief was the same way IIRC. The entire user community customized it into a million different environments tailored to each persons tastes.