From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: UTF-8 characters in comments of a program
Date: Sun, 22 Oct 2023 13:30:40 +0200 [thread overview]
Message-ID: <87v8aynbbz.fsf@dataswamp.org> (raw)
In-Reply-To: IaEOw2FIPJGbrUvHsbmWIBdjKuVNA2yP0vw4uPPz6FfLpNQNrJs9W2PRxLX7ZQhRLaZ0JDwIP6dLsgiVNHPFOnyZoynwSV-hdu6wSefUx20=@protonmail.com
Heime wrote:
>> But in computer-computer technology and programming not so
>> much so IMO. I'm sure modern programming languages that are
>> designed and implemented today can support them, but what
>> is the gain, really? Maybe I'm just old-school.
>
> It is not old-school. It is western-school, because some
> writing systems it is customary to introduce ideograms
> representing concepts or ideas rather than a specific word
> in a language. Examples include Cuneiform, Egyptian and
> Anatolian Hieroglyphs, Mayan, Chinese Scripts, Japanese, the
> list is not short.
The computer revolution - the transistor and later the PC -
are all western things. In particular they are American
things. And what made them possible - the industrial
revolution - is a western thing as well, in particular an
English thing. Pretending to program in another language in
2023 won't change that.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-10-22 11:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 22:53 UTF-8 characters in comments of a program Heime
2023-10-21 7:48 ` Eli Zaretskii
2023-10-21 10:48 ` Heime
2023-10-21 11:24 ` Eli Zaretskii
2023-10-21 11:36 ` Heime
2023-10-21 11:46 ` Eli Zaretskii
2023-10-21 11:51 ` Heime
2023-10-23 15:39 ` Leo Butler
2023-10-21 15:54 ` Basile Starynkevitch
2023-10-21 13:19 ` Jonathon McKitrick via Users list for the GNU Emacs text editor
2023-10-21 13:49 ` Emanuel Berg
2023-10-22 11:04 ` Heime
2023-10-22 11:30 ` Emanuel Berg [this message]
2023-10-22 13:44 ` Eric S Fraga
2023-10-23 5:51 ` Emanuel Berg
2023-10-21 10:25 ` Emanuel Berg
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8aynbbz.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.