From: Van L <van@scratch.space>
To: emacs-devel@gnu.org
Subject: Re: How much I can rely on etc/TODO
Date: Thu, 11 Apr 2019 11:34:24 +1000 [thread overview]
Message-ID: <m2ef69gw9r.fsf@scratch.space> (raw)
In-Reply-To: E1hEL9T-0003Po-IF@fencepost.gnu.org
>> I don't remember Emacs development ever advancing according to plan.
>> It would be nice to have that, I agree, but I don't think it's
>> possible in practice. People work on what they feel like working;
> That's the attitude that Emacs developers have now. But it is not
> inevitable. Let's try to lead and inspire people to work on some
> things that would be a big advance.
Just imagine. A SNERT (or hacker) is at console on those two doomed
Boeing 737 MAX 8 flights, recently. That person using GNU/Emacs
Augmented With AI is able to reason with all available diagnostics data
to within the 40 seconds available and save the day for 360+ passengers.
The robust back-and-forth you witness here between demonstrable experts
should kill the cheapskating single point of failure in design of Boeing
737 Max 8 MCAS, undocumented presence of MCAS, no training for MCAS, and
$80K extra on top of the hefty $120M Boeing 737 Max 8 per aeroplane for
*disagree* instrument panel safety warning light.
FSF: Flight Safety Foundation
next reply other threads:[~2019-04-11 1:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 1:34 Van L [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-08 17:52 How much I can rely on etc/TODO Sameer Rahmani
2019-04-08 17:59 ` Eli Zaretskii
2019-04-08 18:26 ` Sameer Rahmani
2019-04-08 20:42 ` Basil L. Contovounesios
2019-04-08 22:14 ` Richard Stallman
2019-04-09 6:03 ` Eli Zaretskii
2019-04-09 7:50 ` lxsameer
2019-04-09 9:39 ` Eli Zaretskii
2019-04-09 12:05 ` Sergey Organov
2019-04-09 13:52 ` Drew Adams
2019-04-09 23:13 ` Richard Stallman
2019-04-10 15:48 ` Eli Zaretskii
2019-04-10 21:53 ` Richard Stallman
2019-04-11 14:12 ` Eli Zaretskii
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=m2ef69gw9r.fsf@scratch.space \
--to=van@scratch.space \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).