From: Thien-Thi Nguyen <ttn@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: help-gnu-emacs@gnu.org
Subject: Re: General advice beyond Org
Date: Sun, 27 May 2018 20:19:53 +0200 [thread overview]
Message-ID: <87po1hx8om.fsf@gnuvola.org> (raw)
In-Reply-To: <jwv36yd81bm.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 27 May 2018 13:19:41 -0400")
[-- Attachment #1: Type: text/plain, Size: 2247 bytes --]
() Stefan Monnier <monnier@IRO.UMontreal.CA>
() Sun, 27 May 2018 13:19:41 -0400
> > If you add "freedom to do X" you inevitably remove the
> > "freedom from having others do X".
> X is Free Software.
> i write some, share it widely.
> this stops your X how?
Of course, like all tradeoffs, some are trivial because the
downside is negligible. Still, which part of what I wrote do
you dispute?
I'm not disputing anything (at least, i don't think so), besides
the assertion that i'm disputing anything. :-D
My writing that is me scratching my chin, trying a value in a
variable position to see how the expression evaluates.
I suppose i was trying to find X that does / does not fulfill
the zero-sum vibe of what you wrote, expressing my thoughts in a
concise, stylized way.
Still, if a dispute aimed at a particular part must be conjured,
i suppose the word "inevitably" would be the obvious candidate.
My understanding of "freedom from having others do X" hinges on
"having others do X" to mean "delegation of X to others". So,
when X is "writing/sharing free software", we get:
If you add "freedom to w/s free software" you inevitably remove
the "freedom from delegating w/s of free software to others".
This, to my ear, doesn't hold fully. I can imagine myself a
hacker honcho w/ flunkies who i assign to do exactly what i am
trying to do (write/share free software), perhaps even the same
algorithm, for purposes of downstream analysis, deconstruction
and re-synthesis to form the "best" implementation. There is no
no inevitability of removal in this scenario (that i can see).
Anyway, these are new thoughts, so thanks for provoking them!
(My original ponderings were not so profound.) This dispute is
a quite a stretch, anyway (i'm out of practice) -- what am i
missing?
--
Thien-Thi Nguyen -----------------------------------------------
(defun responsep (query) ; (2018) Software Libero
(pcase (context query) ; = Dissenso Etico
(`(technical ,ml) (correctp ml))
...)) 748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2018-05-27 18:19 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.19.1527004804.3124.help-gnu-emacs@gnu.org>
2018-05-23 3:44 ` General advice beyond Org edgar
2018-05-23 19:19 ` Stefan Monnier
2018-05-26 4:14 ` Marcin Borkowski
2018-05-26 19:34 ` Stefan Monnier
2018-05-27 6:54 ` Thien-Thi Nguyen
2018-05-27 17:19 ` Stefan Monnier
2018-05-27 18:19 ` Thien-Thi Nguyen [this message]
2018-05-28 19:21 ` Stefan Monnier
2018-05-31 9:50 ` Thien-Thi Nguyen
[not found] ` <mailman.1113.1528121846.1292.help-gnu-emacs@gnu.org>
2018-06-04 14:46 ` Emanuel Berg
2018-06-04 14:47 ` Emanuel Berg
2018-05-27 18:32 ` edgar
2018-05-23 3:50 ` edgar
[not found] <mailman.893.1527022341.1290.help-gnu-emacs@gnu.org>
2018-05-23 4:23 ` edgar
2018-05-23 4:27 ` edgar
2018-05-23 4:30 ` edgar
[not found] <mailman.626.1526915916.1290.help-gnu-emacs@gnu.org>
2018-05-23 4:04 ` edgar
2018-05-26 4:01 ` Marcin Borkowski
2018-05-26 7:08 ` edgar
[not found] <mailman.15.1526832003.3852.help-gnu-emacs@gnu.org>
2018-05-20 19:29 ` edgar
2018-05-21 3:39 ` Marcin Borkowski
[not found] ` <mailman.148.1526874026.1292.help-gnu-emacs@gnu.org>
2018-05-21 16:26 ` James K. Lowden
2018-05-21 18:07 ` Bob Newell
2018-05-21 19:23 ` Marcin Borkowski
[not found] <mailman.5.1526603344.1292.help-gnu-emacs@gnu.org>
2018-05-18 23:27 ` Gene
2018-05-19 7:06 ` tomas
[not found] ` <mailman.67.1526713619.1292.help-gnu-emacs@gnu.org>
2018-05-27 1:02 ` Gene
2018-05-27 7:27 ` tomas
2018-05-19 22:31 ` James K. Lowden
[not found] <mailman.127.1526629283.1290.help-gnu-emacs@gnu.org>
2018-05-18 8:41 ` edgar
2018-05-21 20:10 ` Eric Abrahamsen
2018-05-22 7:10 ` tomas
2018-05-22 16:58 ` Bob Newell
2018-05-22 18:05 ` Eric Abrahamsen
2018-05-22 19:15 ` tomas
2018-05-18 0:28 edgar
2018-05-18 1:52 ` Peter Neilson
2018-05-18 7:12 ` S. Champailler
2018-05-18 8:10 ` edgar
2018-05-18 8:20 ` tomas
2018-05-18 22:31 ` Stefan Monnier
2018-05-18 8:15 ` tomas
2018-05-18 10:54 ` Yuri Khan
2018-05-18 11:10 ` S. Champailler
2018-05-18 13:50 ` Kevin Buchs
2018-05-18 15:31 ` tomas
2018-05-18 16:19 ` Alan E. Davis
2018-05-18 16:22 ` Alan E. Davis
2018-05-18 16:32 ` Jason Yamada-Hanff
2018-05-18 19:09 ` Devin Prater
2018-05-18 13:50 ` hymie!
2018-05-20 1:24 ` Samuel Wales
2018-05-20 8:08 ` tomas
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87po1hx8om.fsf@gnuvola.org \
--to=ttn@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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.
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).