[Pidgin] #5419: Input field is not resizable

[Pidgin]

#5419: Input field is not resizable
---------------------------+------------------------------------------------
  Reporter:  megaloman     |       Owner:           
      Type:  defect        |      Status:  closed   
  Priority:  minor         |   Milestone:           
 Component:  pidgin (gtk)  |     Version:  2.4.0    
Resolution:  duplicate     |    Keywords:  usability
   Pending:  0             |  
---------------------------+------------------------------------------------
Comment (by deryni):

 First thing: "I don't like" it isn't a reason it is a feeling, we don't
 write code for feelings (unless there isn't anything else involved). We
 aren't ignoring anyone, we are asking people to try the new method and to
 tell us specifically what is wrong with it so we can fix it. No one seems
 to want to do that. No one is telling anyone to "go and fuck yourself".

 Second thing: I am not ignoring any comments, as can be seen from the fact
 that I'm actively trying to respond to them. The comment you quoted has
 *no* reasons in it, just statement of desire, I challenge you to pull out
 a reason from that quote.

 Third thin[g]: Someone took the effort to build it for Windows so people
 can just use it, someone (possibly the same person, I forget) spent time
 explaining the directions required to build it on Windows (the FAQ
 explains how to build plugins on Linux). I'm glad you don't want to use
 the fork, the fork shouldn't have ever happened it isn't worth the effort
 especially as the plugin works.

 No one is telling you what you should and shouldn't like, we are telling
 you we aren't interested in causing ourselves more work simply because you
 like it. If you had reasons that went beyond liking we would consider
 them.

 pidgin is flexible, see for example the manual resizing plugin, keeping
 pidgin full of options is not flexibility it is bloat and pain. Read
 http://pidgin.im/~elb/cgi-bin/pyblosxom.cgi/giving_back.html for a fuller
 explanation of this.

 No argument has been presented beyond "I like it", "I want it", or
 "options are always good you should always keep adding options". All of
 which we have explained why we aren't listening to. The fact that you (and
 the other people who want this back) keep insisting that those are
 arguments and reasons doesn't change the fact that as far as we are
 concerned they are not and that we have explained why. Nor does it mean we
 are immune to reason (if we were we wouldn't have raised the maximum input
 area size to half the window from four lines, people actually argued for
 that change).

 You claim we have thousands of good reasons to make it optional, I claim
 we don't. Prove me wrong, list 5 reasons (that aren't "I like it", "I want
 it", and "options are always good") that we have to make it optional.
 Manage that and you will stand a chance of convincing me/us.

 As I said before no one is saying that. It is also not at all true that no
 users request features to be removed, it happens rather often (generally
 for features they don't use, in the same way that uses only ask for
 features they do use to be added), so any conclusion you draw from that
 idea is flawed at the start. And no, leaving all possible features in and
 constantly adding new features doesn't make anyone happy, neither
 developers nor users is served well by that. It hurts us because it makes
 things harder to do and introduces more bugs; it hurts users because it
 makes it harder to find the things they want, more annoying because they
 get overwhelmed, and means there are more bugs for them to hit.

 I don't even know what point you are trying to make anymore, unless it is
 "options are good, you should always add options, removing options is bad
 for users" in which case we believe that opinion to be wrong (and most
 UI/human interface research agrees with us).

-- 
Ticket URL: <http://developer.pidgin.im/ticket/5419#comment:7>
Pidgin <http://pidgin.im>
Pidgin