zsh-workers
 help / color / mirror / code / Atom feed
From: Keir Mierle <mierle@gmail.com>
To: zsh-workers@sunsite.dk
Subject: Re: Good, easy to use, upstream defaults for zsh (i.e. improving usability)
Date: Mon, 11 Jul 2005 12:13:02 -0400	[thread overview]
Message-ID: <ef5675f3050711091356e9865@mail.gmail.com> (raw)
In-Reply-To: <20050711154439.GA5307@puritan.pnetwork>

On 7/11/05, Nikolai Weibull
<mailing-lists.zsh-workers@rawuncut.elitemail.org> wrote:
> Keir Mierle wrote:
> 
> > On 7/10/05, Mike Hernandez <sequethin@gmail.com> wrote:
> 
> > > On 7/10/05, Keir Mierle <mierle@gmail.com> wrote:
> 
> > > Though I'm not a developer, I can't help but reply to this.   I've
> > > used many linux distributions, and have built linux from scratch
> > > (linuxfromscratch.org). I've also used FreeBSD and OpenBSD, and OS
> > > X.  Each comes with it's own set of defaults (apart from LFS which
> > > has no default zsh config, due to it's being built directly from
> > > source).  Most programs leave any customization to the end user.  If
> > > you use zsh with any of the above mentioned OSes you'll find a
> > > slightly different set of defaults.
> 
> > So what? Did you stop to think for a second, that if the default zsh
> > config didn't suck, then the various distributions might use it?
> 
> How are any of the other shells' defaults any better?

They're not. They're just as awful. This all the more reason to do one better.
Do you think Google, when creating Google Maps, said 'Yahoo maps and
MapQuest can't pan without refreshing, why should we?' No, instead they said
'Hey, we can do something really useful the competition doesn't.'

> > > I would prefer, as an end user, that the developers focus their
> > > efforts on producing the best possible shell, and leave the
> > > customization to us.
> 
> > And as an end user, who on occasion tries to evangelize zsh, I would
> > prefer if developers spent a a small amount of time making zsh work
> > well, by default, most of the time, for most people.
> >
> > Me: Try zsh, it rocks.
> > Friend: Ok, I got zsh. This prompt sucks. How do I fix it?
> > Me: Go get a .zshrc from the net
> > Friend: Ok, completion doesn't complete .pdf's for acroread like you
> > said it would.
> > Me: Go spend hours tweaking your .zshrc.
> > Friend: Gah! Why don't they just include this by default?
> > Me: Beats me.
> > Friend: Screw this, I'm going back to bash. It's available on most
> > platforms anyway,
> > why go through the pain of copying around my .zshrc?
> 
> Same in Bash (for example), no?

Exactly. Bash is just as bad. Which is precisely why we should do one (or two)
better. Which is what we have to do to convince most people to
switch-- the barrier is higher for zsh because it is not installed on
most machines.

> I hear what you're trying to do, but a Z-shell isn't a fish (wow, that
> was a horrible pun),

I'm not suggesting zsh become fish. I am merely suggesting that zsh should not
suck, out of the box, by default.

Thanks,
Keir


  parent reply	other threads:[~2005-07-11 16:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-10 22:37 Keir Mierle
2005-07-10 22:59 ` Mike Hernandez
2005-07-10 23:22   ` Keir Mierle
2005-07-11 15:44     ` Nikolai Weibull
2005-07-11 15:54       ` Travis Spencer
2005-07-11 16:24         ` Nikolai Weibull
2005-07-11 16:35           ` Keir Mierle
2005-07-11 16:13       ` Keir Mierle [this message]
2005-07-11 17:02         ` Nikolai Weibull
2005-07-13  5:44           ` Keir Mierle
2005-07-13  9:23             ` Nikolai Weibull
2005-07-14 12:03     ` Peter Stephenson
2005-07-14 15:06       ` Bart Schaefer
2005-07-14 17:43         ` Peter Stephenson
2005-07-15  0:54           ` Bart Schaefer
2005-07-15  8:58           ` Oliver Kiddle
2005-07-15  9:46             ` Peter Stephenson
2005-07-11  2:58 ` Dan Nelson
2005-07-11 15:45   ` Nikolai Weibull
2005-07-11 15:51     ` Dan Nelson
2005-07-11 15:23 ` Travis Spencer
2005-07-11 15:44   ` Stephen Rueger

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=ef5675f3050711091356e9865@mail.gmail.com \
    --to=mierle@gmail.com \
    --cc=zsh-workers@sunsite.dk \
    /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 public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).