From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Orgdown: negative feedback & attempt of a root-cause analysis
Date: Thu, 02 Dec 2021 12:44:45 +1100 [thread overview]
Message-ID: <87czmfivht.fsf@gmail.com> (raw)
In-Reply-To: <2021-12-02T00-41-46@devnull.Karl-Voit.at>
Karl Voit <devnull@Karl-Voit.at> writes:
> Hi,
>
> I've summarized my current state of mind about the whole Orgdown
> fiasco into a blog article:
> https://karl-voit.at/2021/12/02/Orgdown-feedback/
>
> Don't worry, I tried to analyze my own faults as well so that others
> might be able to learn from this unfortunate situation.
Hi Karl,
thanks for writing up your experiences. I'm not surprised about the
reaction you got from reddit. I gave up on reddit some time back due to
the toxic nature of too many threads. I don't know why it is so often
toxic, but it really isn't worth the hassle.
Starting up a project is difficult. I have an open source JS library
which has turned out to be far more popular than I expected (averages
over 150k downloads each week). I'm not sure I was ready for the
commitment maintaining such a project involves - especially the long
term nature of it. At times, I ahve had problems with rather 'entitled'
users who demand ridiculous things from a free bit of software and who
can become extremely rude and somewhat nasty when I don't do what they
want. I've learnt to just ignore them.
The best advice I can give is to suggest you just put the whole thing on
the back burner for a month or so and then come back to it. During that
time, other comments are bound to come through and I find the later
comments are often far more considered and less emotional than initial
responses. Stepping back gives the subconscious part of your brain time
to process everything and will likely provide additional clarity once it
has had time to percolate.
next prev parent reply other threads:[~2021-12-02 2:36 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 19:46 "Orgdown", the new name for the syntax of Org-mode Karl Voit
2021-11-28 21:34 ` Jean-Christophe Helary
2021-11-28 21:39 ` Bruce D'Arcus
2021-11-28 21:50 ` Tom Gillespie
2021-11-28 22:25 ` Juan Manuel Macías
2021-11-28 22:57 ` Tom Gillespie
2021-11-28 23:16 ` Joost Kremers
2021-11-29 1:36 ` George Mauer
2021-11-29 3:25 ` Juan Manuel Macías
2021-11-29 7:13 ` Dr. Arne Babenhauserheide
2021-11-28 23:24 ` Jean-Christophe Helary
2021-11-29 3:25 ` Devin Prater
2021-12-26 14:54 ` Jean-Christophe Helary
2021-11-29 5:41 ` Marcin Borkowski
2021-11-29 12:18 ` Juan Manuel Macías
2021-11-29 12:36 ` Marcin Borkowski
2021-11-28 22:42 ` Tim Cross
2021-11-29 13:19 ` Karl Voit
2021-11-29 15:12 ` Matt Price
2021-11-29 18:27 ` M. ‘quintus’ Gülker
2021-11-30 7:39 ` Marcin Borkowski
2021-11-30 20:44 ` Orgdown: negative feedback & attempt of a root-cause analysis (was: "Orgdown", the new name for the syntax of Org-mode) Karl Voit
2021-11-30 22:28 ` Dr. Arne Babenhauserheide
2021-11-30 22:50 ` Eduardo Ochs
2021-12-01 0:41 ` Tom Gillespie
2021-12-01 1:12 ` Tim Cross
2021-12-01 3:28 ` Orgdown: negative feedback & attempt of a root-cause analysis Juan Manuel Macías
2021-12-01 21:17 ` Orgdown: negative feedback & attempt of a root-cause analysis (was: "Orgdown", the new name for the syntax of Org-mode) M. ‘quintus’ Gülker
2021-12-02 6:50 ` Orgdown: negative feedback & attempt of a root-cause analysis Eric S Fraga
2021-12-01 23:43 ` Karl Voit
2021-12-02 1:44 ` Tim Cross [this message]
2021-12-02 2:12 ` George Mauer
2021-12-02 8:07 ` Greg Minshall
2021-11-29 2:22 ` "Orgdown", the new name for the syntax of Org-mode Jim Porter
2021-11-29 2:33 ` Michael Ashton
2021-11-29 12:38 ` Max Nikulin
2021-11-29 12:58 ` Christophe Schockaert
2021-11-30 23:50 ` Samuel Wales
2021-11-30 23:56 ` Samuel Wales
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czmfivht.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).