From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Ilya Shlyakhter <ilya_shl@alum.mit.edu>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: BeOrg
Date: Tue, 02 Jan 2018 21:43:14 +0100 [thread overview]
Message-ID: <87373om1p9.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CACfYvRadb2-QrXjzyCMr9aSDRuc8hB5JH9VntvVdQjn_xUdOYQ@mail.gmail.com> (Ilya Shlyakhter's message of "Tue, 2 Jan 2018 14:48:41 -0500")
Ilya Shlyakhter <ilya_shl@alum.mit.edu> writes:
>>as GNU software, we should not suggest to use non-free software
>
> But, clearly, we already do: suggesting to use MobileOrg necessarily
> suggests to use iOS.
>
> Besides, some of the main critiques of non-free software do not apply
> here: e.g. beorg doesn't lock the user into some proprietary format.
I think you are missing the point. Free software is primarily about
source code (the four definitions). Vendor lock-in is but one of the
possible consequences of non-free software. It's still non-free.
> And while it may be unethical to lure unsophisticated computer users
> into freedom-relinquishing decisions the consequences of which they
> may not fully grasp, most Org users are sophisticated enough to make
> an intelligent and informed choice.
Straw man argument.
> GNU itself distributes Emacs for Windows from its main site (
> http://ftp.gnu.org/gnu/emacs/windows/ ), so there's a balance of
> considerations. I think here the balance tips in favor of mentioning
> beOrg. I've tried MobileOrg and gave up on it, while beOrg is more
> usable; judging by the reviews, others had a similar impression.
beOrg may be technically superior, yet usability has never been
a criterion.
Really there's no balance at all: this software doesn't use any of our
libraries and doesn't share our goals. I'm happy someone developed such
software, really, but the way it was done saddens me. If you think that
is worth the shot, you may want to convince its author to turn beOrg
into free software (is that even possible on the Apple store?).
In any case, you may want to discuss this further on gnu-misc-discuss
mailing list, or possibly emacs-devel. For the time being, as far as Org
is concerned, I stand on my ground: there is no reason to reference it
in the manual.
next prev parent reply other threads:[~2018-01-02 20:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 17:32 BeOrg Ilya Shlyakhter
2018-01-02 17:39 ` BeOrg Eric S Fraga
2018-01-02 17:52 ` BeOrg ilya shlyakhter
2018-01-02 19:20 ` BeOrg Nicolas Goaziou
2018-01-02 19:48 ` BeOrg Ilya Shlyakhter
2018-01-02 20:43 ` Nicolas Goaziou [this message]
2018-01-02 22:17 ` BeOrg Peter Davis
2018-01-03 0:30 ` BeOrg Thomas S. Dye
2018-01-03 2:06 ` BeOrg Ian Dunn
2018-01-03 2:43 ` BeOrg Ilya Shlyakhter
2018-01-03 5:00 ` BeOrg Scott Randby
2018-01-03 20:00 ` BeOrg Adonay Felipe Nogueira
2018-01-03 8:26 ` BeOrg Tim Cross
2018-01-03 19:58 ` BeOrg Adonay Felipe Nogueira
-- strict thread matches above, loose matches on Subject: below --
2018-01-05 2:08 BeOrg edgar
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=87373om1p9.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=ilya_shl@alum.mit.edu \
/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).