unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: help-gnu-emacs@gnu.org, Ingemar Holmgren <dag.h@hotmail.se>,
	Henk Pelgrom <henkpelgrom@hotmail.com>,
	Kiki Alfredsson <kikialfredsson@hotmail.com>,
	Greger Eriksson <greger_eriksson@yahoo.com>
Subject: Re: the English language part 2
Date: Mon, 22 Apr 2019 06:13:42 +0200	[thread overview]
Message-ID: <874l6qhe2x.fsf@mbork.pl> (raw)
In-Reply-To: <86k1fnjt0f.fsf@zoho.eu>


On 2019-04-21, at 17:08, Emanuel Berg <moasenwood@zoho.eu> wrote:

> Ralph Seichter wrote:
>
>> Given the sheer number of native Mandarin
>> speakers and China's efforts in computer
>> science (just consider their supercomputing
>> centres), I consider it arrogant to use whe
>> word "never" in your prediction.
>
> The only way that is a possibility is if NATO
> and Russia nuke each other clean of the Earth.

JFF, let me mention that

Arabic
Latin
French

were at some point the lingua francas of the science world (and I could
miss something as well), and none of their respective countries were
nuked.

(And Poland used to be one of the two main powers in Europe one day,
btw., though we used Latin as the language of the elites back then.
Good for all that poor souls speaking Germanic languages - Polish (as
almost any other Slavic language) is basically one huge tongue-twister
for you. :-) )

The US has been in the state of moral and economic decline for a few
decades now.  (I cannot say which is more morally decadent now, the US
or China - apparently China is a terrible authoritarian state, and the
US is quite close, at least since Obama presidency, but probably since
much earlier.)  Economically China might as well win within the next 10
or 20 years.  Such processes are slow, but have very significant
momentum.  So NATO does not have to nuke the US out, the US is currently
doing it to itself (although in a slower and less spectacular way).

Happy Easter anyway,

--
Marcin Borkowski
http://mbork.pl



  parent reply	other threads:[~2019-04-22  4:13 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-21  3:56 title-case function Paul W. Rankin
2019-04-21  5:29 ` Emanuel Berg
2019-04-21  6:40   ` Paul W. Rankin
2019-04-21 10:31     ` `if' in Elisp (was: Re: title-case function) Emanuel Berg
2019-04-21 12:34       ` Drew Adams
2019-04-21 14:02         ` Emanuel Berg
2019-04-21  5:57 ` title-case function Eli Zaretskii
2019-04-21  6:10   ` Emanuel Berg
2019-04-21  6:45   ` Paul W. Rankin
2019-04-21  7:20     ` Eli Zaretskii
2019-04-21  5:57 ` Jean-Christophe Helary
2019-04-21 12:45   ` Paul W. Rankin
2019-04-21 12:59     ` Jean-Christophe Helary
2019-04-21 13:25       ` Paul W. Rankin
2019-04-21 13:58       ` the English language part 2 (was: Re: title-case function) Emanuel Berg
2019-04-21 14:23         ` the English language part 2 Ralph Seichter
2019-04-21 14:32           ` Emanuel Berg
2019-04-21 14:42             ` Ralph Seichter
2019-04-21 15:08               ` Emanuel Berg
2019-04-21 15:21                 ` Ralph Seichter
2019-04-22  4:13                 ` Marcin Borkowski [this message]
2019-04-22  7:55                   ` Paul W. Rankin
2019-04-22 21:21                     ` Emanuel Berg
2019-04-22 21:31                   ` Emanuel Berg
2019-04-25 22:58                   ` Europe in 1648 (was: Re: the English language part 2) Emanuel Berg
2019-04-26 13:40                     ` Ralph Seichter
2019-04-27 21:16                       ` Emanuel Berg
2019-04-29  3:26                         ` Europe in 1648 Van L
2019-04-21 15:22             ` the English language part 2 Drew Adams
2019-04-21 15:38               ` Jean-Christophe Helary
2019-04-21 16:16               ` Emanuel Berg
2019-04-21 13:45     ` title-case function Emanuel Berg
2019-04-21 13:37   ` the English language, again (was: Re: title-case function) Emanuel Berg
2019-04-21 13:38   ` Emanuel Berg
2019-04-22 16:41     ` Robert Thorpe
2019-04-22 21:44       ` Emanuel Berg
2019-04-23  2:35         ` Emanuel Berg
2019-04-24 11:56           ` the English language, again Van L

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=874l6qhe2x.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=dag.h@hotmail.se \
    --cc=greger_eriksson@yahoo.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=henkpelgrom@hotmail.com \
    --cc=kikialfredsson@hotmail.com \
    --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).