From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: History Re: Debunking Emacs merits over GUI - Re: package for Email
Date: Fri, 10 Mar 2023 18:16:27 +0100 [thread overview]
Message-ID: <87ttysv85w.fsf@dataswamp.org> (raw)
In-Reply-To: SJ0PR03MB545515AB49168193D63847D2A2CA9@SJ0PR03MB5455.namprd03.prod.outlook.com
David Masterson wrote:
> I think this thread is kind of missing a key point --
> history. I've been around Emacs for ~40 years (yes,
> TECO Emacs), but I'm, by no means, close to being a
> "Master of Emacs" (we used to call them Gurus). I never had
> time to learn Elisp programming, so I just hacked Elisp code
> together to try out new things (basically setq and
> add-to-hook and, maybe, advise until packages came along) to
> help me with my work.
Interesting, please write more computer history whenever and
as much as you feel like! <3
> There's a lot of history behind what I just said:
>
> 1. The PC Revolution
>
> Mainframes became the backroom land of COBOL that no
> self-respecting college grad would go to. Minis slowly
> disappeared as PCs began making their mark. The problem was
> that it would be 15-25 years before affordable PCs that were
> powerful enough to really support Emacs
Really, that long? :O
> 2. Free Software
>
> 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!).
It's enough that the people who likes it enough to do it,
do it. Gets more real that way and a better community, of
doers and users rather than managers and PR guys ...
> 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.
They don't have to be, there are text-based Android apps and
plugin a physical keyboard and you should have, I don't
know, something. I prefer the comfort of other solutions but
it should be possible, and absolutely so in the long run, for
people who wants that.
> So the next generation of users/programmers are going to be
> "non-GUI challenged".
It's to early to say, as the Chinese Zhou Enlai first premier
said when asked about the significance of the French
revolution ...
> [AI] is an area that I wasn't in, so I can't say much.
> I assume it will lead to more server systems and Linux (and
> Emacs) can ride the coattails. The tools for AI may be more
> in the Linux world, so the landscape could change.
In 1000 years there won't be a single job a human can do -
physical, analytical, mental, even purely emotional if there
are such jobs - that will outperform a machine doing the
same thing.
Programs that program programs should be just around
the corner.
PS. This message is sent by a human being. My name is
Emanuel Berg and I approve this message. And I'm not just
saying that! Heer is a typo to prove I'm not a machine.
Really ...
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-03-10 17:16 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
2023-01-22 3:33 ` David Masterson
2023-03-10 17:16 ` Emanuel Berg [this message]
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=87ttysv85w.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--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).