From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Finding last *Async Shell Command* buffer?
Date: Fri, 26 Mar 2021 22:59:35 +0100 [thread overview]
Message-ID: <87eeg1h8zc.fsf@zoho.eu> (raw)
In-Reply-To: YF4/TYg1DRlcfqh5@protected.localdomain
Jean Louis wrote:
>> Computers are deterministic machines, they don't understand
>> anything. They carry out instructions, that's all.
>
> Fundamentally yes.
By definition.
> However, the more or the better they are programmed the more
> autonomic they may become, so that we do not need to keep
> coding.
What will we then do all days?
But in the future computers will do programming as well if it
continues like that, yes.
> That was direction of coding of 20th century, and we are now
> in 2021. We are late with artificial
> intelligence development.
AI was big in the 70s as well. Because of the tree structure
and data/code blend that Lisp offers, it had an edge there.
You could traverse the trees in different ways, rotate
subtrees, and do stuff like that to, for example, make it
resemble human creativity and intuition. But boil it down, it
was just another way of carry out the same old computation.
A more elegant, cool, and inspiring way perhaps, but still.
The computer remained - a computer.
AI can excel at very simple games, for example chess, which
is well defined and easy to model.
But an AI cannot play ice hockey. It cannot run a bicycle
repair shop or chop wood. Because that's much more difficult!
Put a monitor to your brain when you play ice hockey or
repair bikes. Do the same thing when you play chess. The part
of the brain that is involved when playing chess is a joke.
Go outdoors and talk to a pretty girl. It is more involved.
Chess you can do when you get behind bars. I'm not impressed
by that. So why should I be impressed by the computer
doing it?
In the 60s-70s you could write a PhD thesis about a program
playing chess. Today that would be a big laugh. It is just
a little algorithm that plays chess. As we say, "utvecklingen
har gått framåt" (development has moved forward)
But with AI, what I've seen not so much.
I'd rather take control of the Russian subs and fire off some
nukes at my friend's houses. Ought to teach them not to borrow
my tools never to return them.
So bottom line, if you are here, there is no excuse not trying
to be the best Emacs programmer version of yourself.
Nonchalant code waiting for the AI to help - DNC.
PS. No disrespect to any AI programmer reading this.
Because THAT involves a lot of brain activity. DS.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-03-26 21:59 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 14:33 Finding last *Async Shell Command* buffer? Jean Louis
2021-03-25 15:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-25 15:08 ` Jean Louis
2021-03-25 20:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-25 20:36 ` Jean Louis
2021-03-25 20:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-25 20:59 ` Jean Louis
2021-03-25 21:08 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-25 21:12 ` Jean Louis
2021-03-26 5:52 ` Robert Thorpe
2021-03-26 6:47 ` Eli Zaretskii
2021-03-26 7:04 ` Jean Louis
2021-03-26 7:18 ` Eli Zaretskii
2021-03-26 7:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 7:38 ` Jean Louis
2021-03-26 7:52 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 8:43 ` Jean Louis
2021-03-26 13:37 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 20:08 ` Jean Louis
2021-03-26 21:59 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-03-26 7:17 ` Jean Louis
2021-03-26 7:47 ` Eli Zaretskii
2021-03-26 7:54 ` Jean Louis
2021-03-26 11:31 ` Eli Zaretskii
2021-03-26 14:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 20:11 ` Jean Louis
2021-03-26 22:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 23:28 ` Jean Louis
2021-03-26 23:39 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 7:01 ` Jean Louis
2021-03-26 7:09 ` Eli Zaretskii
2021-03-26 7:25 ` [solved]: " Jean Louis
2021-03-26 7:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 7:40 ` Jean Louis
2021-03-26 7:56 ` Eli Zaretskii
2021-03-26 8:55 ` Jean Louis
2021-03-26 11:18 ` Eli Zaretskii
2021-03-26 11:26 ` Jean Louis
2021-03-26 11:33 ` Eli Zaretskii
2021-03-26 11:48 ` Jean Louis
2021-03-26 12:37 ` Eli Zaretskii
2021-03-26 20:05 ` Jean Louis
2021-03-26 22:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 23:29 ` Jean Louis
2021-03-26 23:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 13:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 10:34 ` Jean Louis
2021-03-26 11:30 ` Eli Zaretskii
2021-03-25 15:18 ` Jean Louis
2021-03-25 15:54 ` Skip Montanaro
2021-03-25 19:31 ` Jean Louis
2021-03-25 18:10 ` Filipp Gunbin
2021-03-25 19:40 ` Jean Louis
2021-03-26 13:09 ` Filipp Gunbin
2021-03-26 13:40 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 20:06 ` Jean Louis
2021-03-26 21:17 ` Filipp Gunbin
2021-03-25 20:05 ` 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=87eeg1h8zc.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).