Live data from Hacker News

Why are libraries destroying books? (2002)

theguardian.com

51–60 of 79 posts

Re: Why are libraries destroying books? (2002)

#51
post #27

Earlier quoted context omitted.

Very rational people here. The moment you tap on libraries, every employee at the library goes on facebook and calls moms to revolt. Its emotion driven, and as a result a political tool.

Every librarian worth their salt knows that weeding is just as important as selection and acquisition. The most emotional people in regards to weeding are often people that read too little, but idolize the object of the book.

See this topic where even tech nerds are idolizing books...

Re: Why are libraries destroying books? (2002)

#52
Library books should definitely destroy shelf litter, like your 900 page "Java: The Complete Reference [2001]" type stuff.

[Edit: When I wrote the above comment, had no idea whether or not this is a real book; I made up the title and the [2001] just to exemplify that sort of junk.]

Re: Why are libraries destroying books? (2002)

#53

Earlier quoted context omitted.

>Sure, some of these tomes may have been recoverable, but if they aren't historically valuable for some reason, why save it? Future historical value is hard to predict. Good example: >Worse is the implication is that if something is not "sufficiently interesting", if it's not part of the story a society wants to tell about itself, it's worthless. The future disagrees about what is and is not important, and why. That'…

So store it digitally where it takes up less space. No need to keep a physical copy around.

> So store it digitally where it takes up less space. No need to keep a physical copy around.

That's a glib answer that ignores the complexity of digital preservation. When you preserve something, you want it to last long term--decades to centuries. Storing things digitally entails choosing software, file formats, and storage media; and the long-term commitment to continuously copy and recopy, convert and reconvert, and test and retest as the technology you choose becomes obsolete. Plus, with digitization, you have the added risk of correctable scanning errors becoming permanent, once the originals are destroyed.

Digital works are some of the most ephemeral ever created, to the point where future historians may experience our era as a kind of dark age:

https://en.wikipedia.org/wiki/Digital_dark_age

Re: Why are libraries destroying books? (2002)

#54
post #16

One of my local libraries recently threw out a dumpster full of books. There was a minor public outcry at the desecration of literature. The books in the dumpster had all been on sale for the last year, priced at 10p (13 cents) each. Most of them hadn't been checked out for over a decade and some hadn't been checked out since the 1970s. Sending books to be pulped is always sad, but the truth is that there are just to…

> Sending books to be pulped is always sad, but the truth is that there are just too many books. Often it's not obsolete books that are destroyed, where there might be 1,000 other copies out there, but one-of-a-kind archival records: >> The core of the book recounts Baker's attempt, in 1999, to persuade the British Library not to junk more than 2,000 bound volumes of American newspapers - the last remaining copies in…

Paper burns. All those paper archives are vulnerable to fires, and indeed much of paper history has been lost to fires.

Digital archives get duplicated (unless the owner jealously hides it away). Duplication is the most resistant means of longevity.

Re: Why are libraries destroying books? (2002)

#55

This seems to be hoarding by proxy. I understand the value of storing the information, but the paper medium itself doesn't typically hold value to me. Is there value in preserving an idiosyncratic style of bound book? Absolutely. Preserving a literal ton of regular old newspapers? Not so much. Let's digitize em and give the libraries room to further modernize so that they can stay relevant.

Yeah, that's my feeling too. No one is "losing" these books. Archival libraries like the Library of Congress exist and are very good at their jobs. (Though I still cry sometimes that the Google Books project didn't work out as originally envisioned).

Local libraries should be serving their community, and that involves making hard choices about spending their existing floor and storage space to make the most useful content available.

Re: Why are libraries destroying books? (2002)

#56

One of my local libraries recently threw out a dumpster full of books. There was a minor public outcry at the desecration of literature. The books in the dumpster had all been on sale for the last year, priced at 10p (13 cents) each. Most of them hadn't been checked out for over a decade and some hadn't been checked out since the 1970s. Sending books to be pulped is always sad, but the truth is that there are just to…

Frankly, if you go look at these stacks of books it is often no mystery why they don't sell.

Re: Why are libraries destroying books? (2002)

#57

Library books should definitely destroy shelf litter, like your 900 page "Java: The Complete Reference [2001]" type stuff. [Edit: When I wrote the above comment, had no idea whether or not this is a real book; I made up the title and the [2001] just to exemplify that sort of junk.]

In 100 years time this book will become of great interest to historians that are studying the dot com boom and wanting insight beyond the newspaper headlines of the era. What was it that powered this dot com thing?

Why was so much money speculated into it?

How hard was it to write code for the early web?

Where is the seminal classic concerning how to program in the language of the era?

Why did 'kazinator' say 'burn that book?'(!)

All this future historian might have to go on could be the review on Amazon, as preserved by the Wayback Machine:

For a supposedly easy-to-use language Java has generated a range of enormous books. The ever excellent Schildt continues the tradition--even allowing for the added coverage of Java 1.3--in this 1,000+ word tome.

Schildt divides the book into four parts. The first third is a solid tutorial on Java programming with neat code examples showing how various features work. Nearly half is taken up with a detailed view of the Java Library followed by 150 pages on Java software development. The last section dissects four Java applets.

Although described as a reference, Java 2: The Complete Reference is a lot more than a list of facts. There's advice, demonstrations of best practice, asides for those using languages such as C and C++ and a pleasant absence of the justifications for various Java design decisions which clog so many books on the subject. Schildt takes the line that Java is the future for Net and networked programs. Coming from perhaps the best-selling writer on C and C++ this is more than interesting. It's a pity Microsoft didn't read it. Perhaps it would have changed its mind about supporting Java.

One oddity is the way Schildt gives more coverage to the largely superseded AWT, the Abstract Window Toolkit, than to its easier and more flexible replacement, Swing. However, both are big areas; perhaps Schildt thinks you should be reading books dealing specifically with these subjects. He'll probably write one. --Steve Patient

Review

First developed in 1991, Java is an excellent first language for the aspiring programmer because of its growing popularity in the development community; seasoned pros will find it easy to learn. Primary among this revised edition's offerings is information on the recently released Java 1.3, known as the 2.0 in the techie world becuase it represents such a major upgrade. Schildt, a renowned programming author, skillfully combines code, theory, and reference matter. Libraries that already own the third edition (1999) should purchase, as Java 1.3 is the only version that Sun Microsystems now supports.

Re: Why are libraries destroying books? (2002)

#58

Library books should definitely destroy shelf litter, like your 900 page "Java: The Complete Reference [2001]" type stuff. [Edit: When I wrote the above comment, had no idea whether or not this is a real book; I made up the title and the [2001] just to exemplify that sort of junk.]

You could plausibly see someone wanting to research the history of programming being interested in such a thing, but in general, you know, there isn't room for everything.

Re: Why are libraries destroying books? (2002)

#59

Library books should definitely destroy shelf litter, like your 900 page "Java: The Complete Reference [2001]" type stuff. [Edit: When I wrote the above comment, had no idea whether or not this is a real book; I made up the title and the [2001] just to exemplify that sort of junk.]

In 100 years time this book will become of great interest to historians that are studying the dot com boom and wanting insight beyond the newspaper headlines of the era. What was it that powered this dot com thing? Why was so much money speculated into it? How hard was it to write code for the early web? Where is the seminal classic concerning how to program in the language of the era? Why did 'kazinator' say 'burn t…

If the book is preserved digitally or otherwise that seems good enough; the library doesn't have infinite space to keep every old book that nobody ever looks at.

Re: Why are libraries destroying books? (2002)

#60
post #5

I would be interesting if there was some type of public disclosure requirement before this type of thing happened. It seems like a perfect setup to allow the general public to collect them.

Libraries will often hold used book sales where they try to unload books they no longer want.

Sounds like the OP envisions something more systematic
Post reply on HN