> If it's a change worth making, you shouldn't have to communicate it.
>
> Your users shouldn't say, how does this work? They should say, this is how it should have worked all along.
I think that this is extremely limiting. I am a moderately skilled vim user, just 'power'ful enough that I have a range of vim-specific tricks up my sleeve, and am frustrated when other editors (seem to) make the same tricks difficult to achieve. However, no one will accuse vim's feature set of being easily discoverable.
By your criterion, it seems that this sort of behaviour, which is hard to learn but powerful once learnt, can be ruled out; and this seems to confine us to a sort of playground where we can perform certain tasks very, very naturally, but are then confined once we need more.
In short, I would change your slogan (which I think is very catchy!) to the less euphonious "Your users should eventually say, 'this is how it should have worked all along'."
I think that this is extremely limiting. I am a moderately skilled vim user, just 'power'ful enough that I have a range of vim-specific tricks up my sleeve, and am frustrated when other editors (seem to) make the same tricks difficult to achieve. However, no one will accuse vim's feature set of being easily discoverable.
By your criterion, it seems that this sort of behaviour, which is hard to learn but powerful once learnt, can be ruled out; and this seems to confine us to a sort of playground where we can perform certain tasks very, very naturally, but are then confined once we need more.
In short, I would change your slogan (which I think is very catchy!) to the less euphonious "Your users should eventually say, 'this is how it should have worked all along'."