Re: Experimentally unbind M-o on the trunk

[Matt Armstrong]

"Alfred M. Szmidt" <ams@gnu.org> writes:

> Why is it always users who have to explain themselves and never the
> developers who change functionality that they don't even seem to use?

In abstract, there are many reasons for this classic pattern of
developer<->user interaction:

 - The developers are trying to make the software better overall, and
   this often requires change.

 - Sometimes there are no remaining active developers on a project that
   actually use a particular feature.

 - The developers are addressing the requests of *other* users, and it
   is not possible to make everybody perfectly happy.

 - It is impossible to read minds, so developers must ask users what
   they need to do and why.

 - Users often don't understand the software as deeply as the developer,
   so the developers ask for what the user wants to actually do, but not
   necessarily the way the user wants the solution expressed.