unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Rusi <rustompmody@gmail.com>, help-gnu-emacs@gnu.org
Subject: RE: Do we want more choice? (was Bookmark the end of file?)
Date: Sun, 12 Apr 2015 22:35:21 -0700 (PDT)	[thread overview]
Message-ID: <291260f3-daa1-4ab4-8840-2ee9b9f164ec@default> (raw)
In-Reply-To: <39b824d1-e8d2-4bf7-a983-c6cefff83dad@googlegroups.com>

> > > > Even if you were right that one use case is more common, why
> > > > wouldn't we want to let users control the behavior, instead
> > > > of deciding it for them at coding time?
> > >
> > > Because offering more choices doesn't always help the user.
> >
> > No, of course not.  But neither does offering fewer choices.
> > How about speaking to this particular question, instead just
> > throwing out truisms?
> 
> There is a general realization nowadays, that everything being
> equal, less choice is likely better than more choice:

"A general realization." "Nowadays." Ooooh. Can't argue with that.

Consideration of one particular choice has now been successfully
diverted toward vacuous generalizations about choice in general -  
platitudes of Polonius.  Too bad.

Not to mention that no one proposed forcing users to choose
anything here.  Define a default behavior.  Provide an easy
way to get other, optional behavior.  No imposition.  No user
paralysis before a terrifying and difficult dilemma.  Perfectly
ignorable choice; zero choosing needed.

I'm afraid you've missed the point. But you were led by example
to miss it.



  reply	other threads:[~2015-04-13  5:35 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06 23:39 Bookmark the end of file? Marcin Borkowski
2015-04-06 23:59 ` Drew Adams
2015-04-07  1:03   ` Marcin Borkowski
2015-04-07  0:00 ` Dale Snell
2015-04-07  1:10   ` Marcin Borkowski
2015-04-07 13:36     ` J. David Boyd
2015-04-07 19:11       ` Marcin Borkowski
2015-04-07 16:49     ` Dale Snell
2015-04-07 19:19       ` Marcin Borkowski
2015-04-07 21:14 ` Stefan Monnier
2015-04-07 22:27   ` Drew Adams
2015-04-12 20:22     ` Stefan Monnier
2015-04-12 20:42       ` Drew Adams
2015-04-12 21:05         ` Stefan Monnier
2015-04-12 21:34           ` Drew Adams
2015-04-13  2:23             ` Stefan Monnier
     [not found]           ` <mailman.528.1428874505.904.help-gnu-emacs@gnu.org>
2015-04-13  3:28             ` Do we want more choice? (was Bookmark the end of file?) Rusi
2015-04-13  5:35               ` Drew Adams [this message]
2015-04-13  7:17                 ` tomas
2015-04-13  7:53                   ` Marcin Borkowski
2015-04-13  8:12                     ` tomas
2015-04-13 14:52                   ` Eli Zaretskii
2015-04-13 19:23                     ` tomas
2015-04-14  7:38                     ` Gian Uberto Lauri
2015-04-14 14:23                       ` Eli Zaretskii
2015-04-14 14:42                         ` Gian Uberto Lauri
2015-04-14 15:30                           ` Eli Zaretskii
2015-04-14 15:37                             ` Gian Uberto Lauri
2015-04-13 17:20                   ` Stefan Monnier
2015-04-13 19:26                     ` tomas
2015-04-13  7:36                 ` Marcin Borkowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=291260f3-daa1-4ab4-8840-2ee9b9f164ec@default \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rustompmody@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).