unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Bob Newell <bobnewell@bobnewell.net>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Debunking Emacs merits over GUI - Re: package for Email
Date: Fri, 20 Jan 2023 12:47:57 +0300	[thread overview]
Message-ID: <Y8pjTUWA+c+RS+7D@protected.localdomain> (raw)
In-Reply-To: <CADoYgq-f9wuRagRe+b4wpmWmHKM-uWd2UzW9MXryCtfLkb1oYA@mail.gmail.com>

* Bob Newell <bobnewell@bobnewell.net> [2023-01-20 00:13]:
> > >Doug Engelbart invented mouse device for people to speed up with
> > >work. Using mouse is just fine.
> 
> Certainly it is.  But remember it is a matter of choice and user
> preference.  I find having to reach for the mouse and remove hands
> from keyboard very disruptive.

That is why makers of Thinkpad placed that red dot button somewhere in
the middle of the keyboard.

> Not to say Thunderbird isn't good.  I actually think it's a very good
> client.  It is just not what I prefer as I like to stay within
> Emacs.

Me too, I stay in `mutt' within or outside Emacs, though can't
recommed that to anybody, I recommed to people who do not know about
terminal applications, only graphicsl Kmail, Evolution or Thunderbird.

> > >It is way too exaggerated and generalized statement. The "powerful
> > >way" in any software comes with experience. To learn what you think is
> > >powerful requires maybe decades.
> 
> This is something I've stressed before.  Serious tools for craftsmen
> require serious effort.  No one starts out as a master craftsman.
> Everyone starts as a novice.  Does that mean that the tools of the
> master are inferior because the novice is not yet skilled with them?
> Hardly.

> I will again say something I've said before.  Emacs is not for
> everyone, and I don't mean that in an elitist sense.  For many of us
> it is an indispensible tool, which we've spent a long while learning
> how to use to best advantage.  For others it may just be a big bother
> when simpler and easier tools may work just fine for their needs.
> 
> I am not out there telling people "learn Emacs" without first knowing
> what their interests and inclinations may be.  That indeed could be
> unproductive.  I think people who can make use of Emacs find their way
> to it eventually.

That is very right.

I think that it is exaggeration with masters and novices, and we
exaggerate with Emacs features, because we love it. But that does not
give realistic picture to people.

Though better be objective towards those users who search for better
e-mail client.

Objectively, Emacs is not an option as e-mail client for anybody.

To understand that reality, simply prepare Emacs with whatever e-mail
client of your choice and bring it to any organization, tell them to
try it out, and then to tell you if they wish to replace  their
ordinary use of e-mail with that one of Emacs. 

Then repeat that with other 2 organizations, then we know what is real
to people.

It is matter of many coincidences and interests and work over periods
of time that somebody becomes "Master in Emacs", and that alone, while
pleasure for those masters, may be pain and impairment for those
considered "novices".

In general people who already use computer are not novices, unless
maybe novices in Emacs. 

Drawing them into that world by saying that Emacs handles better
e-mail is IMHO less productive for their life.

When user starts maintaining e-mail server, of course that user may
start learning about IMAP, about `procmail', or `sieve' and maybe some
users maintain multiple servers, for that type of users is alright to
engage into complexities as they can handle it. It does not mean they
are "masters" just because they maintain web servers, there are many
GUI interfaces for web servers, mail servers and similar. 

When user handles e-mails with family and business, then graphical
programs like Thunderbird may be appropriate.

So we always better start from human, from people, instead from
a program (Emacs vs Thunderbird).

Human is the reason for program. Programs are made with purpose to
assist human.

Not other way around.

Emacs, Thunderbird itself is not reason in itself for human to use
them. People should not use programs because their underlying power is
demonstratable, but because programs will help them handling their
life.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  reply	other threads:[~2023-01-20  9:47 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 13:56 package for Email Gottfried
2023-01-18 14:44 ` Eric Brown
2023-01-18 15:15 ` Jean Louis
2023-01-19  7:31   ` Tomas Hlavaty
2023-01-19  7:55     ` Jean Louis
2023-01-18 15:51 ` Tassilo Horn
2023-01-18 17:17   ` Eli Zaretskii
2023-01-18 17:58     ` andrés ramírez
2023-01-19  3:55       ` Jean Louis
2023-01-18 16:28 ` Andreas Eder
2023-01-18 18:03 ` Milan Glacier
2023-01-19  4:02   ` Jean Louis
2023-01-19  5:06   ` Debunking Emacs merits over GUI - " Jean Louis
2023-01-19  5:41     ` Emanuel Berg
2023-01-19 13:00       ` Jean Louis
2023-01-19 15:34         ` Marcin Borkowski
2023-01-20  8:27           ` Jean Louis
2023-01-19 16:10     ` Milan Glacier
2023-01-19 16:52       ` Jude DaShiell
2023-01-20  9:32         ` Jean Louis
2023-01-19 21:10       ` Bob Newell
2023-01-20  9:47         ` Jean Louis [this message]
     [not found]           ` <877cxgrc3e.mmmtqrm@thhcbmmmd.mijofcrcc.org>
2023-01-21  7:05             ` Jean Louis
2023-01-21  7:20               ` Emanuel Berg
2023-01-21  7:21               ` Eli Zaretskii
2023-01-21  7:28                 ` Emanuel Berg
2023-01-21 14:29                   ` Jean Louis
2023-01-21 14:28                 ` Jean Louis
2023-01-21 15:31                   ` Eli Zaretskii
2023-01-21 17:30                     ` Bob Newell
2023-01-22 15:40                       ` Jean Louis
2023-01-20  9:07       ` Jean Louis
2023-01-20 15:52         ` Milan Glacier
2023-01-21  6:04     ` History " David Masterson
2023-01-21  7:10       ` Eli Zaretskii
2023-01-21  7:21         ` Emanuel Berg
2023-01-21  7:34         ` tomas
2023-01-21 17:38         ` Bob Newell
2023-01-22  3:16           ` David Masterson
2023-01-22 15:48           ` Jean Louis
2023-01-22  3:08         ` David Masterson
2023-01-22  6:23           ` Eli Zaretskii
2023-01-22 19:33             ` David Masterson
2023-01-22 19:57               ` Eli Zaretskii
2023-01-22  7:45           ` Po Lu
2023-01-22 19:35             ` David Masterson
2023-01-21 14:35       ` Jean Louis
2023-01-22  3:33         ` David Masterson
2023-03-10 17:16       ` Emanuel Berg
2023-03-13  8:32         ` Po Lu
2023-01-18 18:10 ` Filipp Gunbin
2023-01-19  2:15 ` Emanuel Berg
2023-01-19 12:40   ` Jean Louis
2023-01-19 14:10   ` Martin Steffen
2023-01-19 16:20     ` Eric S Fraga
2023-01-19 16:39       ` Jude DaShiell
2023-01-20 10:05         ` Jean Louis
2023-01-19 17:00       ` Leo Butler
2023-01-19 17:35         ` Eric S Fraga
2023-01-20  6:48       ` Milan Glacier
2023-01-19  3:53 ` Jean Louis
2023-01-19  6:08 ` John Haman
2023-01-19 11:52   ` Emanuel Berg
2023-01-21 13:57     ` Jean Louis
2023-01-21 15:08       ` Jude DaShiell
2023-01-21 17:47       ` Bob Newell
2023-01-22  3:46         ` David Masterson
2023-01-22 19:52           ` Bob Newell
2023-01-22  3:34     ` David Masterson
2023-01-31  5:46       ` Emanuel Berg
2023-01-20  4:09   ` Milan Glacier
2023-01-20  7:31     ` Emanuel Berg
2023-01-20 10:26     ` Jean Louis

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=Y8pjTUWA+c+RS+7D@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=bobnewell@bobnewell.net \
    --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.
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).