Awful Library Books
awfullibrarybooks.net
awfullibrarybooks.net
"Note the “groovy” cover."
"I want to weed this one based on the home decorating in the last picture below."
Here's how amazon reviewers felt about the book:
"Just what I needed to use my vintage sewing machine feet more effectively which was original intent when I bought the book but wow'd by the great info for sewing and illustrations. Great resource book to have whether beginner or advanced"
"This book is great if you have any older vintage Singer machines."
"It's the complete guide. Good for beginners to experienced. 72 yrs old male. father was upholster, mother drapery and seimstress, Good for helping me out for what I forgot"
- https://awfullibrarybooks.net/sewing-fundamentals/ - https://www.amazon.com/Singer-Sewing-Book-Complete-Guide/dp/...
Also, the groovy cover is awesome.
For most libraries, I think so. By which I am referring to general purpose community libraries. They have limited space, and keeping books on hand that nobody looks at is not a good use of that space. I wouldn't expect any of the public libraries in my area to keep obscure titles that are rarely touched.
Some other libraries purpose to be more of an archive, a repository of knowledge; I would expect such libraries to be slower to discard things.
Really, though, this seems like a great opportunity for scanning and digital preservation... copyright woes aside...
Now you've traded your problems of having one collection with having two. Not to mention the choice (and constant migration!) of hardware media, data formats, etc. Are you going to be able to even read these digital files fifty years from now? Who's going to maintain this? Are you going to add a whole IT dept to your local library to keeping this system running?
None of this is impossible, of course. But it's not free and it's not trivial.
But it shouldn't be a job for every local library. All that is needed is one copy of the book; not every copy of the book. And for more recent books, there shouldn't even be a need to scan it; there should already be a digital version (whether if it was made publicly available or not).
Granted, long-term storage and viewing of digital files seems like an open-ended problem in itself, regardless of who is handling it. But so is long-term storage and viewing of physical books. The books take up space, must be handled with care, and will deteriorate eventually (though hopefully slowly as preservation methods have advanced).
I get that angle, but IMO there are some things that legitimately fall into that category, to a degree. Things that benefit others, or "society in general", but not me in particular.
For instance, I get no direct benefit from paying for public education (I'm done with school myself, no children), but I like to live in a society that is generally educated. So, I happily pay my taxes.
I suppose this might somehwat go against your "nor do I intend to contribute to its upkeep" provision, but I don't particularly track down and intentionally discover just every which way my tax dollars are spent, yet still I think its a good idea to pay that money, for the various things it provides for various people, even if it's not me directly.
Or to bring it back to the discussion at hand: It seems reasonable to wish (though not expect, per se) that a library has certain books available to the community, even if I don't personally read them. It's the fact that nobody is checking them out that makes them a waste of space in this particular instance.
Just my 2¢.
That is precisely why a public library should get rid of it. There's a limited amount of shelf space; a 60-year-old book which nobody is reading is a waste of that space.
I wonder if they're just trolling with scanned books they've found online?
For example, this is from the entry for the 1957 book "Rocket Power and Space Flight".
"The author talks to the “fellows” who wrote him letters and uses the pronoun “he” and “him” throughout the book. Reason #1 to weed it."
Sure, this is an old book and would probably get weeded anyway. But why make such a big deal about community members objecting to material when you yourself object to so much material?
JFC. This was taught as standard usage until very recently. It's silly to fault a book published before, I dunno, 2010 or so if I'm being generous, for that.
I used to find this website entertaining, but this is quite disappointing.
Like other groups of humans, librarians have diverse opinions.
Honestly I wouldn't limit it to "historians or other academics." I'd think having a collection immaculately-curated for the present day sensibilities would create/reinforce a false impression that the present is timeless. I think it's good to come into contact with everyday things the reflect the recent past, even if it's just to get a sense of motion. And (realistically) the only place where that might be possible with books is a community library.
Not a fan of the over-opinionated framing. It seems like mainly a list of things that are "dated" (which I'd personally find pretty interesting, for various reasons) and/or politically incorrect from the author's orientation.
Skimming through the first few pages, I see some very good examples of "dated" books which should absolutely be weeded, including:
* A book about jobs "for the new millennium" written in 1999 (https://awfullibrarybooks.net/apply-within/)
* A book about the HIV epidemic written in 1989 (https://awfullibrarybooks.net/hiv-aids-from-the-1980s/)
* A book on "Video Games: how it's made" written in 1996 (https://awfullibrarybooks.net/how-about-a-career-in-video-ga...)
* A "teen guide to birth control" from 1988 (https://awfullibrarybooks.net/teen-guide-to-birth-control/)
* A directory of self-help groups and hotlines from 1989 (https://awfullibrarybooks.net/get-some-help/)
Some of these books may have some limited historical interest. That's fine. But that doesn't mean they should be in a public library, especially when they run the risk of misrepresenting historical information or beliefs as truth.
> A book on "Video Games: how it's made" written in 1996 (https://awfullibrarybooks.net/how-about-a-career-in-video-ga...)
That book looks interesting, and the blogger's justification for weeding it is "I don't understand video game development", not "there is a more modern book to use instead".
The possibility that a modern book may be incorrect does not override the fact that older books about rapidly changing topics (like the book on HIV/AIDS) will contain information which has been superseded or disproven, or that compilations of time-sensitive information (like the 1989 directory of self-help groups) are useless when they become outdated.
> That book looks interesting, and the blogger's justification for weeding it is "I don't understand video game development"...
The more detailed justification is: this is a simple book (48 pages, large type, lots of pictures) made for children. Nuances like "computers don't use BASIC anymore" or "the video game industry has changed a lot since then" are likely to be lost on them -- and, to be frank, there was never a lot of concrete information in the book to begin with.
https://archive.org/details/videogames0000erlb/page/32/mode/...
* The author conflates the NES with all "home game systems". An entire chapter titled "how it works" describes the NES (in very broad terms) without ever acknowledging the existence of other game systems -- not even the SNES, which came out six years before the book was published.
* There are some unforced technical errors in the book, like claiming that a device called a "synthesizer" is used to "translate [sounds] into computer codes", or that "with an RGB monitor, the signals go straight from the CPU to the screen". This is not a carefully researched and written book. It's an author's quick swing at "kids like video games, we should write a book about those".
* Despite what you might assume from the excerpt, the book does not actually provide any actionable information about game programming. The BASIC snippet seen on the web site is only used to motivate a claim that games contain "lots and lots of commands", not to suggest that the reader can program a game.
I was expecting some truly awful stuff with hilarious commentary in the vein of the Gallery of Regrettable Food, but most of this is just 'This book is old and has outdated information and therefore is awful in terms of suitability for a public library collection'.
Well, except for the 'Build your own bazooka at home' one, I guess.
> Weeding is an essential component of library collection management. Most libraries simply do not have unlimited space, and we must continually make room for new materials. Weeding is necessary to remain relevant to our users and true to our missions. Remember – *unless your library exists to archive and preserve materials for the ages*, we are not in the business of collecting physical things. We collect information and provide access to information. We love books as much as anyone else, and sometimes hard decisions have to be made. How many times have you said, “But I just bought that!” and then realized it was ten years ago?
https://en.wikipedia.org/wiki/Five_laws_of_library_science#T...
These people are not librarians. They are censors.
https://news.ycombinator.com/item?id=27325095 ("Book Review: Double Fold")
There's a rumor that some three-letter agencies surreptitiously published "subversive" literature containing explosives-related recipes of this ilk in the hope that people inclined to build bombs would use the recipes to take themselves out of the gene pool.
Not a single citation from the content?
If this were a tenth grade essay, I would give it a D.
@cjlm Please don't submit garbage to HackerNews.
Weeding is hard.