| I understand the romantic appeal of discovering "abandoned" books and forgotten ideas. However I suspect my reaction to your anecdote is very different to the one that most people might have, because I think that behaviour is harmful to the library. ( A very minor harm, but a harm nonetheless. ) They have identified books that people don't borrow, and have made it clear they want to get rid of them. That's to benefit the library, catalogue and storage isn't free and endless. So they have a signal that no-one is borrowing these books, and they can replace it with books that do get borrowed. Along you come and interrupt that signal, in a way that doesn't have underlying desire to borrow that book. So the clock gets reset, and so it goes. In software development terms, imagine you develop a product with a number of features with a public API, and telemetry points that a feature goes unused. You want to clean up the code so you mark some endpoints as deprecated and list that in your change log. Now imagine there's a developer who looks at the changelog for deprecation warnings, then goes out their way to develop apps that call them. "Unloved books" might seem more romantic than un-called API endpoints, but the library needs to rotate and refresh to stay healthy. If you want unloved books, then pick them up for next to nothing from the sale outside the library, most libraries will practically give away books they've rotated out, and you're actually doing them a favour "disposing" of them while likely giving them a token amount of money for it. |
A deprecation marker is a "this will be removed"; these markers are "this will be removed if nobody reads them even with this marker in them".