all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: use-package
Date: Sat, 14 May 2016 00:37:43 -0700 (PDT)	[thread overview]
Message-ID: <9a592c77-4531-414a-a644-988800cdbeb6@googlegroups.com> (raw)
In-Reply-To: <mailman.2761.1463153947.7477.help-gnu-emacs@gnu.org>

On Friday, May 13, 2016 at 9:09:09 PM UTC+5:30, Drew Adams wrote:
> Making a blanket, one-size-fits-all judgment for everyone
> takes choice away from users. 

:
:

> I'm all for such a possibility.  What I am not for is
> Emacs imposing or recommending this or that look & feel
> in some blanket way.
> 
> Let a hundred flowers bloom.  Vive the mode line.


etc
Just consider me in the opposite camp.
Everything else being equal too much choice is a bad thing:

https://www.ted.com/talks/barry_schwartz_on_the_paradox_of_choice

One could go further and DEFINE freedom as choicelessness.
While I wont do that I will say that emacs is progressing from the
best software category to suxware category by offering too much bogus choices

- .emacs.d/init.el or .emacs 
- custom-file or let customize mess your init
- setq or customize
- half a dozen options to specify keybindings
- eval-after-load or add-hook or simple-setq (+prayer that the mode author 
followed norms)

I could go on
But I think you get the idea -- Choice is undesirable if there is any choice 
about making the choice

Most recent example of bogus choices
haskell mode has been upgraded to some new fancy beyond-comint stuff
But the old comint is still there -- if you like -- Choice after all is wonderful.
Result: What used to work OTB now needs to have explicit define-keys to make 
sure user chooses old or new interface


  parent reply	other threads:[~2016-05-14  7:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02 17:07 use-package Uwe Brauer
2016-05-02 18:47 ` use-package Kaushal Modi
2016-05-03 10:47   ` use-package Uwe Brauer
2016-05-03 14:01     ` use-package Kaushal Modi
2016-05-03 22:28       ` use-package Stefan Monnier
2016-05-04  3:33         ` use-package Kaushal Modi
2016-05-04 12:09           ` use-package Stefan Monnier
2016-05-04 16:22         ` use-package Phillip Lord
2016-05-04 16:44           ` use-package Drew Adams
2016-05-05 13:34             ` use-package Phillip Lord
2016-05-05 14:00               ` use-package Drew Adams
2016-05-05 15:56                 ` use-package Kaushal Modi
2016-05-05 16:12                   ` use-package Drew Adams
2016-05-10  9:20                     ` use-package Phillip Lord
2016-05-10  9:18                   ` use-package Phillip Lord
2016-05-11 11:42                     ` use-package Kaushal Modi
2016-05-12 21:04                       ` use-package Phillip Lord
2016-05-13 11:56                         ` use-package Stefan Monnier
2016-05-14 22:27                           ` use-package Phillip Lord
2016-05-15  3:22                             ` use-package Stefan Monnier
2016-05-13 15:38                         ` use-package Drew Adams
2016-05-16 15:16                           ` use-package Phillip Lord
2016-05-16 16:49                             ` use-package Drew Adams
     [not found]                         ` <mailman.2761.1463153947.7477.help-gnu-emacs@gnu.org>
2016-05-14  7:37                           ` Rusi [this message]
2016-05-10  9:13                 ` use-package Phillip Lord
2016-05-05  9:51       ` use-package Uwe Brauer
2016-05-05 13:38         ` use-package Phillip Lord
2016-05-03 22:21 ` use-package Stefan Monnier
2016-05-05 10:15   ` use-package Uwe Brauer
2016-05-05 23:41     ` use-package Stefan Monnier

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

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

  git send-email \
    --in-reply-to=9a592c77-4531-414a-a644-988800cdbeb6@googlegroups.com \
    --to=rustompmody@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.