I'd like to see a good book on error handling. I feel this is still one of the great unsolved problems of software engineering (alongside naming) and most programming books just don't do it and say something like "obviously this is not production code but error handling would clutter up the examples too much". That to me is indicative of the problem.
I like the project based book idea. Physically Based Rendering is a rather nice example of this but I don't know of too many other similar books in other domains.
I think it's hard for code to be beautiful when it's mostly glue (calling libraries) rather than implementing a basic task (like sorting). As such, most modern (glue) languages are less likely to evoke aesthetic wonder in the reader than might a simpler, low level language like C or Pascal.
There are som fine guides online, but they usually don't have the scope or "budget" of a book. That being said, I loathe those massive 1500 page tomes that brand themselves as an "introduction" to the subject (I mean that first book in the linked article, "Introduction to Algorithms", 1300 pages), it really demotivates me when thinking about having to delve into those to learn the basics.
It would be nice with books in the 200-300 page range, and maybe doing project based books to teach the ropes and pitfalls of a technology would solve that. Then there's the possibility to make follow-ups with more intermediary topics or projects.
My long term side project has been to bootstrap an independent publishing house focused on technical topics. I'm always looking to hear what programming books people think are missing in the market.
Some recurring topics I keep seeing are more books on the soft skills / career development side of things, and more project based books that help you learn how certain technologies work internally by building a database, queue system, web framework, etc. from scratch.