Flutterby™! Culling the hard...copy 2003-10-13 21:15:57.922831+00

So, speaking of books, I've decided that I need to do a big culling of my bookshelves. I'm not sure quite how far down I want to dig, but some questions:

1. Should I keep my copy of Newman & Sproull? How about the other classics that I don't have a reason to go back to, Aho, Sethi & Ullman's Compilers: Principles, Techniques and Tools, Clocksin and Mellish on Prolog, Kernighan and Plauger's Software Tools, the classics that probably most modern geeks haven't heard of? Some of these might be useful for archivists some day, looking at the Human Interface Guidelines for the Apple Desktop Interface could show some interesting things about how GUIs evolve, but should I care?
2. How about books for obsolete APIs and hardware. Any reason to care about COM any more? How about Norton's Programmer's Guide to the IBM PC?
3. And process books? From Jane M. Healy's Failure to Connect to Steve McConnell's Writing Solid Code to The Inmates Are Running The Asylum, many of these were lauded, some I liked, some I didn't, will I ever have a reason to go back?

And, perhaps the most important question: On the ones I don't see a need to keep, should I throw 'em out, or does someone out there want 'em?

[ related topics: Apple Computer Books Software Engineering Writing Archival Failure To Connect ]