Articles About Free Books



Download 95.92 Kb.
Page6/7
Date16.08.2017
Size95.92 Kb.
#32735
1   2   3   4   5   6   7

You mean like Wikipedia?


Five years ago, people looked at me funny when I expressed my enthusiasm for free books. You mean like Project Gutenberg? Downloading Hamlet for free? No no, I explained, I was talking about books intentionally set free by their authors. Huh? You know, like Linux. Open-source books. You mean like that party game where you sit in a circle, and everybody takes turns making up the next part of the story? No no no, I'd explain, serious tomes on weighty subjects: calculus, Proust, cell biology. This would be received with a look of pity, or maybe a hint that I might need to talk to a mental health professional.

These days the response is, "Oh, you mean like Wikipedia?"

That's progress. In 1950, science fiction author Robert Heinlein (of Stranger in a Strange Land fame) was asked by the editor of a science fiction magazine to make serious predictions of what the world would be like in the year 2000.[2] At that time, Heinlein's fictional depictions of 2000 featured a lot of flying cars, but in his nonfiction article he did say some sensible things about how progress actually works. Progress is exponential. Over the short term, an exponential curve doesn't look very impressive, and if you extrapolate it linearly, you won't think anything all that exciting is going to happen. But in the long term, the curve goes ballistic. Johann Gutenberg thought his printing press would allow people who weren't quite so rich to have their own Bibles. He would never have imagined the public library, much less the internet.

Giving it away isn't free.


The most notable recent progress in the world of free books is that a kind of infrastructure is starting to come together to support them. This article is the third in an intermittent series. In the first one,[3] written in 2000, a big barrier I pointed out was the problem with the lack of appropriate open-source software for desktop publishing: you have to eat your own dog food, and there was no way that open-source books would ever get off the ground if they had to be produced using an array of expensive and mutually incompatible closed-source software. But since then I've learned the hard way that software wasn't the only barrier. Although my second article,[4] in 2002, was wildly optimistic, I was finding that my own physics textbooks, which I'd tried to set free in the wild, were acting like twenty-somethings who couldn't afford to move out on their own because their jobs at WalMart were just barely paying for their car insurance. Professors at other colleges were adopting my books, which was exciting, but those professors wanted printed copies for themselves and their students. One day I woke up and found myself running a small business --- and it wasn't just small, it was small, inefficient, time-consuming, and unprofitable. I had forgotten the flip side of Heinlein's dictum of exponential progress: although we tend to underestimate for the far future, we also tend to overestimate for the near future. Flying cars didn't happen by 2000, because, well, for one thing you couldn't yet find a service station that sold plutonium. The infrastructure wasn't there yet. I think the infrastructure for free books is only now starting to be built, which is why, although there are now over 1000 free books listed on a web site I run that catalogs them,[5] those thousand books have still had relatively little impact.

One of those thousand books is Wikipedia, and although it's atypical in many ways, Wikipedia is a particularly dramatic illustration of one of the infrastructural problems I'm talking about: bandwidth. The Wikimedia Foundation depends on an international server farm consisting of over a hundred machines.[6] On a smaller scale, bandwidth is going to be an issue for anyone serving up a popular, illustrated book. As my own books have been downloaded more and more, my webhosting costs kept escalating, eventually reaching $100 a month.[7] The authors of one free organic chemistry textbook[8] have gone so far as to throttle back the load on their server by requiring prospective readers to register and give an e-mail address before they can access the book. The problem is that many of those prospective readers will balk, and that will keep the book from gaining mind-share --- college professors are used to being courted assiduously by book reps, and to getting so many unsolicited books sent to them by publishers that they can use them as doorstops.

I've also learned what a capital-intensive business print publishing is. With traditional printing technology, the unit cost goes down dramatically as the length of the press run increases, and that economic imperative meant that I soon had about $10,000 invested in a closet full of books. Meanwhile, my wife, who handles the family finances, was warning me that I was losing money. Webhosting, printing, and advertising were adding up to more than I was bringing in.

the new infrastructure


The whole business of free books was harder than I'd though it would be, so hard that it probably would have deterred most prospective authors if they'd known what they were getting into. One of the lessons of Wikipedia's success is that you have to make things easy for authors; its philosophy of instant gratification was the reason it did so well where its stuffier, slower-moving predecessor Nupedia had failed. One item of good news is that within the last few years, it's become possible for a someone who isn't an ubergeek to create an illustrated textbook using open-source software. Scribus, a GUI desktop publishing application, makes it easy to do a book with a complex visual layout, something that could previously be done using LaTeX, but only with the sacrifice of many goats. Inkscape, a 2003 fork of the open-source illustration program Sodipodi, has made rapid progress, and is now in the same league as Adobe Illustrator. PDF, long treated with suspicion by the free software community, has emerged as a lingua franca for online books, and there is now a hefty toolchain for creating and working on PDF files, including Scribus, Inkscape, and a long-awaited 1.x release of PdfTex, as well as many smaller utilities such as pdftk and pdfripimage. Color management had for a long time been a shortcoming of Linux compared to Windows and MacOS, partly due to patents, but is now incorporated into a few Linux applications such as Scribus via the littlecms color management system. OpenOffice's ability to read Microsoft Word documents has also helped to alleviate the former problem of authors finding that once they had written something in Word format, they were forever locked into proprietary software.

One justification offered by publishers for the astronomical prices of college textbooks is the high cost of permissions fees for materials such as photographs, artwork, or anthologized text. Since September 2004, the free information community has had a weapon in its arsenal that's unavailable to traditional publishers: Wikimedia Commons, a repository containing hundreds of thousands of photos.[9] Since most of the images are under copyleft licenses, they can be used in copylefted free books, but not in traditional copyrighted books. Although five years ago many of us who were interested in free books envisioned the sharing of copylefted words, in fact it looks like the commonest currency of collaboration is turning out to be not text but pictures. A positive development related to this has been the increasing standardization of licenses. There's a pretty clear consensus these days that new copylefted materials should be licensed either under the Creative Commons Attribution-ShareAlike license or the GNU Free Documentation License, or both.[10] As a textbook author, dual licensing my books under these two licences allows me to legally use essentially 100% of the contents of Wikimedia Commons. Even for an author who has no particular interest in free information as an abstract ideal, the use of non-proprietary photos opens up the possibility of using free digital copies of a book as sales tools. That's an option that traditional publishers don't have, because permissions fees are computed according to how widely the book is distributed.[11]

But even if there's no legal objection to giving your book away for free, there's still that pesky issue of the cost of bandwidth. Luckily there's some new infrastructure coming along to take care of this as well. Jason Turgeon has founded a site called textbookrevolution.org,[12] whose mission is to mirror free books and take the load off of authors. The Wikibooks project, which aims to extend the success of Wikipedia to the creation of a whole library of books, is backed by the horsepower of the Wikimedia Foundation server farm. And finally, there's an interesting company called lulu.com,[13] dating back to 2002, which is opening up new possibilities for distributing books, both electronically and in print.



Download 95.92 Kb.

Share with your friends:
1   2   3   4   5   6   7




The database is protected by copyright ©ininet.org 2024
send message

    Main page