From: Tobias Geerinckx-Rice <somebody@not-sent-or-endorsed-by.tobias.gr>
To: mikadoZero <mikadozero@yandex.com>
Cc: Guix-devel@gnu.org
Subject: Re: Guix pronunciation
Date: Sun, 10 Mar 2019 18:20:28 +0100 [thread overview]
Message-ID: <87r2behcir.fsf@nckx> (raw)
In-Reply-To: <y35mu2po.fsf@yandex.com>
Hullo!
Now I personally think ‘Guix’ looks and sounds good (not fine),
and our logo is positively stunning, and damn professional too.
If that makes me biased, so be it ;-)
mikadoZero wrote:
> I also wanted to know what people think about the "geeks"
> pronunciation and how it may impact adoption of Guix as it
> continues
> to grow long term. Maybe someday becoming as popular as Debian,
> macOS or Windows are today (wishful thinking). For example what
> if
> Linux kernel had actually been called Freax. […] Would it have
> negatively impacted adoption of the kernel.
I really don't think so. ‘Linux’ is the fellow's name with an X
on the end. It's as much of a anti-marketing joke as ‘Freax’ was
(or GNU or Guix for that matter). The only reason it seems more
familiar is because, well, it is.
And (honest question): do we even care? Such a stupid reason to
shoot yourself in the foot with an inferior package manager.
> Yes Freax and "geeks"
[and “Linux”]
> are fun. On the other hand branding is important.
You wrote this as a contradiction but I don't see one.
The world's most valuable and evil company was once called
‘Google’. Koooky!
> Just to make my bias clear. I am not a fan of pronouncing Guix
> "geeks" and find myself thinking of deliberately mispronouncing
> Guix as "gwixs" or spelling out the letters G U I X when talking
> to people about Guix.
That's really unfortunate.
Kind regards,
T G-R
GUIX® is a trademark of Express Logic, Inc. All other brands or
product names are the property of their respective holders.
next prev parent reply other threads:[~2019-03-10 17:20 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 [this message]
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
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2behcir.fsf@nckx \
--to=somebody@not-sent-or-endorsed-by.tobias.gr \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).