From: Leo Famulari <leo@famulari.name>
To: mikadoZero <mikadozero@yandex.com>
Cc: Guix-devel@gnu.org
Subject: Re: Guix pronunciation
Date: Tue, 12 Mar 2019 00:52:42 -0400 [thread overview]
Message-ID: <20190312045242.GA4065@jasmine.lan> (raw)
In-Reply-To: <y35mu2po.fsf@yandex.com>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
On Sun, Mar 10, 2019 at 12:13:55PM -0400, mikadoZero wrote:
> I think the confusion around the pronunciation of GIF would probably be
> a worst case scenario.
Non-techies rarely discuss JPEGs or PNGs, while GIFs are a cultural
phenomenon.
How to pronounce 'GIF'? Anyone can weigh in, and it doesn't require any
technical knowledge.
After 30 years, GIF has come to mean 'a brief moving image on a
computer'. It's a tremendous success! A harmless controversy can be
endearing :) I can't think of a single downside for GIF.
On the other hand, I think the most important property of a name is that
it does not change. Google indexes written words, not pronunciation. A
long tail of articles and discussion of Guix is extremely valuable.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-03-12 4:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 16:13 Guix pronunciation mikadoZero
2019-03-10 17:20 ` Tobias Geerinckx-Rice
2019-03-11 2:45 ` mikadoZero
2019-03-11 22:32 ` George Clemmer
2019-03-10 17:21 ` Tobias Geerinckx-Rice
2019-03-12 12:48 ` Ludovic Courtès
2019-03-12 13:05 ` Laura Lazzati
2019-03-12 13:12 ` Pierre Neidhardt
2019-03-12 13:21 ` Laura Lazzati
2019-03-13 14:10 ` Ludovic Courtès
2019-03-13 15:08 ` Laura Lazzati
2019-03-15 1:10 ` mikadoZero
2019-03-10 17:51 ` sirgazil
2019-03-11 1:43 ` mikadoZero
2019-03-11 21:26 ` Laura Lazzati
2019-03-11 21:06 ` L p R n d n
2019-03-11 23:51 ` Leo Famulari
2019-03-12 4:52 ` Leo Famulari [this message]
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=20190312045242.GA4065@jasmine.lan \
--to=leo@famulari.name \
--cc=Guix-devel@gnu.org \
--cc=mikadozero@yandex.com \
/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/guix.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.