All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Satchell <satch@fluent-access.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	kernel@Expansa.sns.it (Luigi Genoni)
Cc: linux-kernel@vger.kernel.org
Subject: Re: When the FUD is all around (sniff).
Date: Tue, 26 Jun 2001 07:38:05 -0700	[thread overview]
Message-ID: <4.3.2.7.2.20010626071942.00b9b380@mail.fluent-access.com> (raw)
In-Reply-To: <E15Es2e-0003T1-00@the-village.bc.nu>
In-Reply-To: <Pine.LNX.4.33.0106261015120.9537-100000@Expansa.sns.it>

At 01:34 PM 6/26/01 +0100, Alan Cox wrote:
>It is common for newspaper staff to be corrupt, same with magazine people.
>Sometimes because people generally believe in a cause and are not impartial
>(which I've seen both pro and anti Linux btw) and sometimes because 
>advertising
>revenue is a good thing.

Alan, never attribute to conspiracy that which is adequately explained by 
stupidity.  You would be surprised how often newspaper and magazine 
reporters and their editors make gaffs like this with absolutely no intent 
of malice, or with the sole malice of wanting to write an article that will 
be "interesting" to a large readership while taking insufficient time to 
check all the facts.

When I worked at a magazine as a staffer, I was amazed when the 
editor-in-chief, in response to complaints about a columnist who "got it 
wrong" a lot, said that he kept the columnist on because his mistakes 
attracted readership.  "He gets TONS of letters, and the readers can't wait 
to see how he screws up next!"  Again, not by intent, but by incompetence.

For reporters, it's not a matter of "not caring," it's a matter of being 
required to knock out 15 articles in one day (not uncommon for a reporter 
on a major metropolitan newspaper) and not having to hand references that 
are willing to provide answers quickly.

Final comment:  Know what a well-adjusted paranoid is?  "Hey, they ARE out 
to get you, but it's nothing personal."

Satch


  parent reply	other threads:[~2001-06-26 14:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010618134644.A5938@egregious.net>
     [not found] ` <20010618145331.A32166@wacko.asicdesigners.com>
     [not found]   ` <20010621161349.A27654@egregious.net>
2001-06-25 21:06     ` [PATCH] skb destructor enhancement idea Will
2001-06-25 22:34       ` David S. Miller
2001-06-25 22:50         ` Will
2001-06-25 23:12           ` David S. Miller
2001-06-26  8:35           ` When the FUD is all around (sniff) Luigi Genoni
2001-06-26 12:33             ` Alessandro Suardi
2001-06-27 21:08               ` Fabrice Gautier
2001-06-26 12:34             ` Alan Cox
2001-06-26 14:59               ` [OT] " Jordan Crouse
2001-06-26 15:02                 ` Alan Cox
2001-06-26 15:09                   ` Jonathan Lundell
2001-06-26 17:41                     ` Rob Landley
2001-06-26 15:06                 ` Jonathan Lundell
2001-06-26 15:28                 ` Luigi Genoni
2001-06-26 22:47               ` lk
2001-06-27 12:44               ` Marco Colombo
2001-06-26 14:19             ` Stephen Satchell
2001-06-26 14:38             ` Stephen Satchell [this message]
2001-06-26 15:16             ` Jonathan Corbet
2001-06-26 16:43               ` Rik van Riel
2001-06-26 17:00               ` Kip Macy
2001-06-27  0:29 Schilling, Richard
2001-06-27 10:30 ` lk

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4.3.2.7.2.20010626071942.00b9b380@mail.fluent-access.com \
    --to=satch@fluent-access.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=kernel@Expansa.sns.it \
    --cc=linux-kernel@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.