Books are a great source of knowledge, yes, and there are a few other things that make book reading, especially programming books, much more valuable.

Patience : For obvious reasons

Focusing on a topic for longer duration : This applies to reading any book (not just programming/coding books)

Attention to detail : Videos/blogs etc are good for "high" level learning (yes, even video courses with 50 episodes are high-level learning), and when you are reading a book you have to give your full attention to the line/paragraph/section that you are reading, because it is not someone else teaching (that you can skip or lose-track-of), it is you who is reading and until the subject matter is clear in your head you would not be able to move on to the next section/line. So it becomes paramount that we have to give attention to the details mentioned therein.

Problem understanding : In a programming book, the problems are laid out in a detailed manner, and it requires intense focus and attention to understand the given problem (so that when the solution/answer is discussed in subsequent sections/chapters, you can grab that).

Problem solving : Once you have understood the problem, it is equally important to solve the problem as well, and when you are reading a book and the author is taking you through the detailed steps of solving the problem, you understand the journey (and not just the solution)

Slow gratification process : Once you have started a book, the journey begins to explore the details on various topics (depending on the subject of the book), and the emotional satisfaction of finishing a book makes up for a slow, but very high gratification, which makes you happy, and as a programmer, makes you more confident and allows you to be more communicative and sharing (very important things that you cannot achieve via videos/blogs etc)

Organised reading/follow-up : Finishing a book makes you understand the intricacies of content-writing (and eventually code-writing), and helps you become a more organised developer, especially around managing the non-coding content. JIRA/Trello stories, understanding documentation of 3rd party APIs/other-platforms, improving upon the instinct/gist of going through various docs and enables you to find the required/focused content sooner. The more you read organised and complete content (books), the more you improve your intuition and you grow faster-reading skills , without missing on the key information (which is a huge cause of frustration for developers, since they tend to skip a lot of seemingly-insignificant content while reading the project/task details and end-up with half-baked features/products

This is in no way a complete list of the good things that happen to you (as the reader/programmer) when you read a programming book, but this should help you understand the importance of reading books (hard-copies, not e-books).

Perhaps the only post in 2021, on December 31'st