Web development books are written with the knowledge that they will be toilet paper in 4 years. So they are written as fast as possible and are really bad, most often.
If you are reading more than a chapter a week from a technical book, you're doing it wrong.
You are suppose to read a chapter, practice what you learned over the week and read the next chapter. If you read a technical book cover to cover in a single week, you will understand less than a person that reads a single chapter twice.
Technical books are not fantasy novels, you will need to know the last chapter word for word to understand the next, there is no reading between the lines.
>they write as many words as possible to have the thickest book in town, explaining relatively straightforward concepts in terms a nigger can understand
That is good, when you are teaching people, you want to explain every concept in great detail. Unless the book calls itself an advanced book on a subject, it should explain everything in detail.
Would you prefer:
CPUs have registers.
Addition operations are done like so
ADD EAX 50;
or
CPUs have a limited number of registers which have different names such as EAX EBX..etc Registers have a limited number of bytes to store data
A CPU may perform an addition operation on registers using the mnemonic "ADD", for example
ADD EAX 50;
This operation will store the value 50 in the EAX register