From: Paul Rankin <paul@tilk.co>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: pirate bay, w3m, and the interface is just an interface (BEST post ever)
Date: Sun, 14 Dec 2014 15:45:41 +1000 [thread overview]
Message-ID: <m2fvcikcmy.fsf@tilk.co> (raw)
In-Reply-To: <jwvr3w2n7hf.fsf-monnier+gnu.emacs.help@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> at 15:14 on 14 Dec 2014:
> Most illegal copying doesn't hurt any artist, but only hurts companies
> that engage in entertainment. Notice that they don't call themselves
> "the cinema industry" but "the entertainment industry", and indeed
> 99% of it has nothing to do with art.
It seems that this kind of naive armchair perspective is spouted so
profusely that its validity is taken prima facie. No, the companies in
question don't gnash their teeth and take the losses, they pass them on,
mostly to their predominately middle-class workforce, but also by
shifting output to focus exclusively on opening-weekend,
merchandise-friendly fare and away from anything "cinematic" in the
Steven Soderbergh sense. It is myopic to suggest piracy has no affect on
cinema-as-art when it has all but killed it.
Please don't perpetuate this kind of false Robin Hood myth, it's
wilfully ignorant self-interest under a thin veil of trumped up "people
vs the system" garbage. Whatever of this self-deception one practices,
the truth is piracy is stealing from real people.
next prev parent reply other threads:[~2014-12-14 5:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 0:46 pirate bay, w3m, and the interface is just an interface (BEST post ever) Emanuel Berg
2014-12-14 1:57 ` Paul Rankin
2014-12-14 5:14 ` Stefan Monnier
2014-12-14 5:45 ` Paul Rankin [this message]
2014-12-14 8:22 ` Marko Vojinovic
2014-12-14 9:40 ` Paul Rankin
2014-12-14 14:46 ` Óscar Fuentes
2014-12-14 15:08 ` Paul Rankin
2014-12-14 18:31 ` Óscar Fuentes
2014-12-14 18:39 ` Marcin Borkowski
2014-12-14 19:00 ` Óscar Fuentes
2014-12-14 14:59 ` Marcin Borkowski
2014-12-14 22:18 ` Stefan Monnier
[not found] ` <mailman.16023.1418550049.1147.help-gnu-emacs@gnu.org>
2014-12-23 5:50 ` Emanuel Berg
2014-12-14 13:19 ` Stefan Monnier
2014-12-14 14:03 ` Paul Rankin
2014-12-14 15:20 ` Thien-Thi Nguyen
2014-12-14 15:25 ` Paul Rankin
2014-12-15 8:30 ` Thien-Thi Nguyen
[not found] ` <mailman.16063.1418578427.1147.help-gnu-emacs@gnu.org>
2014-12-14 17:54 ` Rusi
2014-12-14 15:22 ` Paul Rankin
2014-12-14 14:01 ` Marcin Borkowski
2014-12-14 14:39 ` Paul Rankin
2014-12-14 16:08 ` Rasmus
2014-12-14 22:08 ` Stefan Monnier
[not found] ` <mailman.16048.1418567978.1147.help-gnu-emacs@gnu.org>
2014-12-17 21:28 ` Ted Zlatanov
[not found] ` <mailman.16020.1418545381.1147.help-gnu-emacs@gnu.org>
2014-12-14 9:02 ` Rusi
2014-12-14 9:43 ` Paul Rankin
2014-12-23 5:39 ` Emanuel Berg
[not found] ` <mailman.16043.1418565713.1147.help-gnu-emacs@gnu.org>
2014-12-23 5:59 ` Emanuel Berg
[not found] ` <mailman.16017.1418535962.1147.help-gnu-emacs@gnu.org>
2014-12-23 5:36 ` Emanuel Berg
[not found] ` <mailman.16010.1418522266.1147.help-gnu-emacs@gnu.org>
2014-12-22 22:08 ` Emanuel Berg
2015-03-24 13:52 ` Glen Stark
2015-03-25 0:54 ` Emanuel Berg
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=m2fvcikcmy.fsf@tilk.co \
--to=paul@tilk.co \
--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).