Forthcoming 2nd ed. of _The Ruby Way_

Bill G. wrote:

I’m sure you know all of this, but just the same…

You should point them to the success of AWDWROR [1]. It certainly is
a new/controversial idea, but it seems to be win/win.

Some counterpoints for consideration:

  • In contrast to offering a free online version (if even only prior to
    publication) the pay-to-preview approach means you get fewer eyeballs
    and have fewer bug reports & suggestions prior to publication.
    Open-to-all improves quality.

  • It is indeed great for publishers, because they get consumers to
    commit cash early, where waiting for the book to be finished risks
    potential buyers opting to spend their money elsewhere. First to
    market has a big advantage. But how does the buyer “return” and get a
    refund for a PDF download?

James

http://www.ruby-doc.org - Ruby Help & Documentation
Ruby Code & Style - Ruby Code & Style: Writers wanted
http://www.rubystuff.com - The Ruby Store for Ruby Stuff
http://www.jamesbritt.com - Playing with Better Toys
http://www.30secondrule.com - Building Better Tools

On 12/15/05, James B. [email protected] wrote:

  • In contrast to offering a free online version (if even only prior to
    publication) the pay-to-preview approach means you get fewer eyeballs
    and have fewer bug reports & suggestions prior to publication.
    Open-to-all improves quality.

Without a doubt, it would, but I think it would be a tough sell to
publishers who seem to be convinced that it would reduce future sales.
Pay-to-preview may mean fewer eyeballs than a free preview, but it’s
more eyeballs than no preview (the traditional approach).

  • It is indeed great for publishers, because they get consumers to
    commit cash early, where waiting for the book to be finished risks
    potential buyers opting to spend their money elsewhere. First to
    market has a big advantage. But how does the buyer “return” and get a
    refund for a PDF download?

I don’t pretend to have the answer to that one. Others far smarter
than me have been stumped by it for decades.

Currently, return policies are up to the producer of the content. As
long as they make that policy known, I can make an informed choice
when I decide whether or not to buy a digital version.

Over the years, I’ve bought many books, but only a few PDFs. I
haven’t wanted to return any of them. For now, I’m really not all
that concerned about return policies – but that’s just me.

  • It is indeed great for publishers, because they get consumers to
    commit cash early, where waiting for the book to be finished risks
    potential buyers opting to spend their money elsewhere. First to
    market has a big advantage. But how does the buyer “return” and get a
    refund for a PDF download?

I think that the problem here is that with digital content of any kind,
the protections that you enjoy as a consumer are usually obsoleted by
the goods being digital.

I can go into a shop and buy a packaged application (for me it’d most
likely be a game, lets say Civ IV as it’s new and happening), then a
week later I take it back. Suddenly the store won’t accept it and my
consumer protections that are valid for say a lawnmower or a washing
machine are no longer valid for a computer game. Obviously I understand
the reasoning as games can (and often are) pirated, so essentially the
shops don’t trust their consumers when it comes to digital goods, but
with physical products it’s ok

My favourite quote (to finish with this off-topic-ness) comes from Bruce
Schneier -“Making digital files not copyable is like making water not
wet

</totally off topic here>

Bill G. wrote:

Pay-to-preview may mean fewer eyeballs than a free preview, but it’s
more eyeballs than no preview (the traditional approach).

I’ve had authors tell me they would never again offer a book for free
online. Yet others swear by it. It is not uncommon for O’Reily to
offer current books online for free (as part of their Open Books
project), and Bruce Eckel seems pleased with is results. APress offers
Practical Common Lisp for free, too. (Good book!) And Mark W. is
currently working on a Ruby book that he says will be available as a
free PDF.

It’s not that unusual; it is perhaps something of a tradition of its own
in geek publishing. But, yes, if you are tying to lock down every
dollar, it may be too much of a risk. It’s a business, and people have
to find the model that gets them the results they want.

James

http://www.ruby-doc.org - Ruby Help & Documentation
Ruby Code & Style - Ruby Code & Style: Writers wanted
http://www.rubystuff.com - The Ruby Store for Ruby Stuff
http://www.jamesbritt.com - Playing with Better Toys
http://www.30secondrule.com - Building Better Tools

James B. wrote:

a new/controversial idea, but it seems to be win/win.
publishers who seem to be convinced that it would reduce future sales.

It’s not that unusual; it is perhaps something of a tradition of its
own in geek publishing. But, yes, if you are tying to lock down every
dollar, it may be too much of a risk. It’s a business, and people
have to find the model that gets them the results they want.

James

I find that having a print book does several things for me: It lets me
get my eyes away from the screen for a while; it gives me something
productive to do in planes, trains, and automobiles (Passenger seats
only :wink: and it is a nice distraction at times such as during TV
commercials or while sitting on the can (Preferable to staring at the
wall.)

Because of these many advantages I will usually buy a print book if it
is of interest to me even if the same material is available online for
free or reduced cost. Having the material online is an added value,
though, because I can search it more easily when I need a quick answer
at work. Generally, however, I will not pay for an online version,
because I would rather have the print version (And I’m certainly not
going to pay twice for the same content.)

On Fri, Dec 16, 2005 at 11:12:32PM +0900, Bill G. wrote:

Without a doubt, it would, but I think it would be a tough sell to
publishers who seem to be convinced that it would reduce future sales.
Pay-to-preview may mean fewer eyeballs than a free preview, but it’s
more eyeballs than no preview (the traditional approach).

I tend to think that a reduction in future sales isn’t so much what
they’re worried about, even if publishers say it is. Most people with
that kind of decision-making authority at a successful publishing house
are smart enough to see the advertising potential and product
improvement potential in pre-releasing an incomplete or unpolished work,
if you point it out to them and make a halfway decent case for it. Yes,
there’s some risk of reduced sales, but it’s miniscule in comparison
with the potential return in increased sales, especially if there is
secific material that will only be available in the paid-for version
still to come.

What it really boils down to, I think, is the common desire to get
dollars from everyone who would be willing to part with them. The “lost
sales” they worry about likely aren’t really any reduction in total
number of sales: handled even semi-competently, you can gain more sales
than you’d lose by doing an electronic pre-release, even for free. With
current intellectual property laws and expectations in the US, however,
people in IP-related industries just have a problem tolerating the
thought that anyone got to “experience” what they’re selling without
paying for it, regardless of whether that actually hurts revenue
streams.

Obviously, there are exceptions, and thank goodness O’Reilly is one of
them. A personal example of an exception working out in the publisher’s
favor is the Pragmatic Programmers’ Ruby books: I used wget to download
a copy of the Pickaxe book so that I’d always have it handy whether
online or not. After reading it, I was inspired to pick up a copy of
their Rails book, for which I shelled out cover price (minus my member
discount at the bookstore). I’m now planning to pick up the Pickaxe2,
again for cover price (minus the member’s discount at the bookstore).

This may not work as well for fiction (for instance), but I’m not really
interested in electronic copies of novels anyway. It sure as heck works
for technical references, though.


Chad P. [ CCD CopyWrite | http://ccd.apotheon.org ]

unix virus: If you’re using a unixlike OS, please forward
this to 20 others and erase your system partition.