all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: Flipping url-show-status default
Date: Sun, 03 Oct 2010 18:34:42 -0400	[thread overview]
Message-ID: <m3bp7ac3c5.fsf@jhcloos.com> (raw)
In-Reply-To: <87iq1jigo1.fsf@lifelogs.com> (Ted Zlatanov's message of "Sun, 03 Oct 2010 07:50:38 -0500")

>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:

TZ> I think you're underestimating the amount of time and expertise that
TZ> went into the Chrome and Firefox UI design.  They are quite good.

I use ff for sites with faulty ui detection logic and seamonkey as my
primary gui browser.  It is precisely true that the ff ui is crap
compared to sm (which tries to keep the mozilla ui).  Everything they
could do to make the ui worse is done, from removing regularly-used
menu items, to making the context menus harder to use, to breaking the
keyboard ui, et al.

Nearly every "cool" idea they came up with makes it harder to get work
done.  And the one good change they made wasn't even their idea;
changing the appearance of the uri bar for encrypted links was proposed
years earlier in the crypto community.  Kudos to the ff team for finally
getting the concept into gecko, and for many of the lower-level changes
they made.  But very much not for the majority of their ui changes.

The ff team may *think* they improved the zilla ui, but anyone who has
extensively used both can attest that that is a fallacy.

Following /their/ tradition of ui redesign is a poor idea.

If emacs' progress info is too noisy to follow, then I'm all for
cleaning it.  Just please do not eliminate it, or simplify it
beyond what it needs.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6



  reply	other threads:[~2010-10-03 22:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01 14:20 Flipping url-show-status default Lars Magne Ingebrigtsen
2010-10-01 14:56 ` Ted Zlatanov
2010-10-01 18:13 ` Chong Yidong
2010-10-01 18:23   ` Lars Magne Ingebrigtsen
2010-10-01 22:17     ` Chong Yidong
2010-10-01 22:20       ` Lars Magne Ingebrigtsen
2010-10-01 22:29         ` Chong Yidong
2010-10-02  2:06           ` Lars Magne Ingebrigtsen
2010-10-02  2:23             ` Lars Magne Ingebrigtsen
2010-10-02  2:24               ` Lars Magne Ingebrigtsen
2010-10-02  2:58             ` Chong Yidong
2010-10-02 13:07               ` Lars Magne Ingebrigtsen
2010-10-01 18:34   ` Ted Zlatanov
2010-10-01 22:21     ` Chong Yidong
2010-10-02  7:23       ` Eli Zaretskii
2010-10-02 15:13       ` Ted Zlatanov
2010-10-02  7:34     ` James Cloos
2010-10-02 14:54       ` Ted Zlatanov
2010-10-02 19:21         ` James Cloos
2010-10-03 12:50           ` Ted Zlatanov
2010-10-03 22:34             ` James Cloos [this message]
2010-10-05 16:51 ` Davis Herring
2010-10-05 16:58   ` Lars Magne Ingebrigtsen

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=m3bp7ac3c5.fsf@jhcloos.com \
    --to=cloos@jhcloos.com \
    --cc=emacs-devel@gnu.org \
    --cc=tzz@lifelogs.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.
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.