I disagree. All books are released too early if you think about it. The technology will change rapidly no matter when you buy the book so it's up to the buyer to make sure it's the latest release for the version they'll be working with if a version applies.
Let's take nodejs for example. I think it's safe to say that it's new enough to be considered too early to publish if there were such a thing. Even if node changes drastically within the next few months any book about any technology that's worth anything at all (did I say anything enough times? Haha) will teach you the fundamentals about how to get it, set it up, configure it how you want, and get you going with some reproduce able examples. That's really all you need. No book can be expectd to cover every last bit of the technology in great detail. I'd argue that most people learning to program get the fundamentals from the books and maybe some bonus knowledge and the rest we pick up with experience and research.
Then you have remember that there's a good bit of time between the writing of the book and it's publishing and then some more time between editions. No book can be current. But it doesn't matter because of why we buy the books to begin with. We learn the ropes from them. Even books about advanced techniques teach you enough about a technology so that in a case where the advanced technique is out of date you can still get what you want done by inferring how you're supposed to do things now based on other data from the book combined with experience and practice. So given all this, I don't think there's a such thing as being released too early and in fact believe all books are released too late. But they're valuable nonetheless.
Let's take nodejs for example. I think it's safe to say that it's new enough to be considered too early to publish if there were such a thing. Even if node changes drastically within the next few months any book about any technology that's worth anything at all (did I say anything enough times? Haha) will teach you the fundamentals about how to get it, set it up, configure it how you want, and get you going with some reproduce able examples. That's really all you need. No book can be expectd to cover every last bit of the technology in great detail. I'd argue that most people learning to program get the fundamentals from the books and maybe some bonus knowledge and the rest we pick up with experience and research.
Then you have remember that there's a good bit of time between the writing of the book and it's publishing and then some more time between editions. No book can be current. But it doesn't matter because of why we buy the books to begin with. We learn the ropes from them. Even books about advanced techniques teach you enough about a technology so that in a case where the advanced technique is out of date you can still get what you want done by inferring how you're supposed to do things now based on other data from the book combined with experience and practice. So given all this, I don't think there's a such thing as being released too early and in fact believe all books are released too late. But they're valuable nonetheless.