From: Munyoki Kilyungi <me@bonfacemunyoki.com>
To: Janneke Nieuwenhuizen <janneke@gnu.org>,
paul <goodoldpaul@autistici.org>
Cc: Nathan Dehnel <ncdehnel@gmail.com>, atai@atai.org, guix-devel@gnu.org
Subject: Re: The e(macs)lephant in the room and the Guix Bang
Date: Mon, 02 Oct 2023 14:23:41 +0300 [thread overview]
Message-ID: <87bkdh469u.fsf@saitama.mail-host-address-is-not-set> (raw)
In-Reply-To: <87msxdfbuy.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]
Janneke Nieuwenhuizen <janneke@gnu.org> aliandika:
[...]
>>
>> Thank you for your opinion but it's just that: a subjective judgement
>> based on your own episodic experience.
>
> I'm sorry if my tone was too harsh, I now realise this is still
> triggering old pain.
>
> Why is it still OK to for people to keep spreading negative anecdotes
> about Emacs, and problematic to refute them or counter them with
> positive anecdotes?
>
> It's been me believing exactly such lies that scared me away from
> starting with Emacs for years, lost years in a way; something I deeply
> regret: this has to stop.
>
This I agree with. I got into Emacs about a
decade ago. And what helped me I guess, was that
no one in my environment used Emacs nor knew too
much about it. And the internet wasn't as fast as
it is now. So in a sense, I got into the
ecosystem "by faith", and it stuck. However, this
is not the case today. I'm running a SICP reading
book club community locally, and the feedback I'm
getting from people who are trying it out, is that
it's "very difficult to learn", and most of these
sentiments are from the internet.
--
(Life is like a pencil that will surely run out,
but will leave the beautiful writing of life.)
(D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
(hkp://keys.openpgp.org))
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2023-10-02 11:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 5:19 The e(macs)lephant in the room and the Guix Bang Nathan Dehnel
2023-09-23 7:37 ` Janneke Nieuwenhuizen
2023-09-23 8:58 ` paul
2023-09-23 10:00 ` Janneke Nieuwenhuizen
2023-09-24 7:37 ` Nathan Dehnel
2023-09-24 8:51 ` Liliana Marie Prikler
2023-09-25 11:19 ` MSavoritias
2023-09-25 18:54 ` Liliana Marie Prikler
2023-09-25 19:21 ` Simon Tournier
2023-09-25 11:09 ` MSavoritias
2023-09-25 20:34 ` Emacs and Guix (was Re: The e(macs)lephant in the room and the Guix Bang) Simon Tournier
2023-09-28 7:19 ` Efraim Flashner
2023-10-02 11:23 ` Munyoki Kilyungi [this message]
2023-09-23 12:59 ` The Giraffe; the Pelican et al " indieterminacy
2023-09-25 11:13 ` MSavoritias
2023-09-25 20:35 ` Simon Tournier
2023-09-26 7:33 ` indieterminacy
2023-09-23 9:56 ` The e(macs)lephant in the room and the Guix Bang Ricardo Wurmus
2023-09-23 10:25 ` Ricardo Wurmus
2023-09-23 12:29 ` Ricardo Wurmus
2023-09-24 7:11 ` Nathan Dehnel
2023-09-24 20:19 ` Csepp
2023-09-24 21:46 ` Ricardo Wurmus
2023-09-27 18:38 ` Christine Lemmer-Webber
2023-09-28 6:12 ` Nathan Dehnel
-- strict thread matches above, loose matches on Subject: below --
2023-09-20 18:00 Andy Tai
2023-10-02 14:56 ` Ludovic Courtès
2023-08-23 16:25 How can we decrease the cognitive overhead for contributors? Katherine Cox-Buday
2023-08-24 6:33 ` (
2023-08-26 0:39 ` Katherine Cox-Buday
2023-08-27 3:22 ` Maxim Cournoyer
2023-08-27 7:39 ` 宋文武
2023-08-28 11:42 ` Giovanni Biscuolo
2023-09-01 19:12 ` Imran Iqbal
2023-09-03 17:45 ` Ekaitz Zarraga
2023-09-03 21:05 ` indieterminacy
2023-09-03 21:16 ` Ekaitz Zarraga
2023-09-13 12:20 ` Fannys
2023-09-13 15:42 ` Maxim Cournoyer
2023-09-17 11:29 ` MSavoritias
2023-09-18 10:09 ` Simon Tournier
2023-09-19 16:35 ` The elephant in the room and the Guix Bang Giovanni Biscuolo
2023-09-20 8:21 ` Csepp
2023-09-20 8:45 ` The e(macs)lephant " Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-09-20 9:28 ` MSavoritias
2023-09-20 14:03 ` Ricardo Wurmus
2023-09-20 14:09 ` MSavoritias
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=87bkdh469u.fsf@saitama.mail-host-address-is-not-set \
--to=me@bonfacemunyoki.com \
--cc=atai@atai.org \
--cc=goodoldpaul@autistici.org \
--cc=guix-devel@gnu.org \
--cc=janneke@gnu.org \
--cc=ncdehnel@gmail.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).