unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: David Masterson <dsmasterson@gmail.com>
Cc: Milan Glacier <news@milanglacier.com>,
	Gottfried <gottfried@posteo.de>,
	"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: History Re: Debunking Emacs merits over GUI - Re: package for Email
Date: Sat, 21 Jan 2023 17:35:46 +0300	[thread overview]
Message-ID: <Y8v4QlQEfH4g1G9J@protected.localdomain> (raw)
In-Reply-To: <SJ0PR03MB545515AB49168193D63847D2A2CA9@SJ0PR03MB5455.namprd03.prod.outlook.com>

* David Masterson <dsmasterson@gmail.com> [2023-01-21 09:10]:
> While RMS' goal may have been laudable, many (most) programmers could
> not see how to monetize their work in a free software environment and,
> so, went where the money was more plentiful.  Without the investment of
> big bucks that copyrighted software could command, development of Emacs
> in the 90s slowed to a crawl and depended on the programmer "with an
> itch".  Good stuff was done, but it could've been so much more.  This is
> why Emacs development took 40 years whereas things might've happened
> faster in the more capitalistic world (but Emacs would've been very
> different beast!).

I agree to your points. Though if you say that Emacs could have been
more suitable to general public if it would be proprietary, maybe yes,
but it would not be extensible.

As proprietary decisions would lead to control of people, and
extensibility features are not part of it. 

And proprietary Emacs would not include too many features, as they
would be wasting resources, and not bringing money, as you said.

> 5. Smartphones
> 
> The iPhone is still not capable of supporting Emacs and I don't know how
> well Android could support Emacs.  Even if they could support Emacs,
> Smartphones are GUI-intensive, so not really an environment for a text
> editor. So the next generation of users/programmers are going to be
> "non-GUI challenged".

Right.

Emacs runs without problem in Termux for Replicant/Android and similar
systems. There is nice tap-keyboard, with CTRL, ALT, etc. which is
locked, user can basically use single finger to get all Emacs
commands. 

There is effort on Emacs Development mailing list to make Emacs for
Android with GUI.


-- 
Jean

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

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



  parent reply	other threads:[~2023-01-21 14:35 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
     [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 [this message]
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=Y8v4QlQEfH4g1G9J@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=dsmasterson@gmail.com \
    --cc=gottfried@posteo.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=news@milanglacier.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).