Ignore everything he said except this: "They are an introductory peek at what is cool about a complex subject. Then you have the opportunity to learn more about the parts the interested you..."
It's not a book that'll teach you how to actually do any of this stuff. It's an overview, a gloss, an extended Wikipedia entry in guide form, that shows you the work that goes into creating a programming language. It's like the show "How It's Made." If, at the end, you think you actually want to write a programming language, then by all means, read your set of books. (That's not to say that this was their goal--it was probably a stupid attempt to actually let people design and implement a language after reading one book--but this is what you should take away from it, and a perspective from which reading the book would be useful.)
It's not a book that'll teach you how to actually do any of this stuff. It's an overview, a gloss, an extended Wikipedia entry in guide form, that shows you the work that goes into creating a programming language. It's like the show "How It's Made." If, at the end, you think you actually want to write a programming language, then by all means, read your set of books. (That's not to say that this was their goal--it was probably a stupid attempt to actually let people design and implement a language after reading one book--but this is what you should take away from it, and a perspective from which reading the book would be useful.)