> 15 years ago, I read a dozen of C++ books cover-to-cover. Can someone today get similar levels of knowledge jumping around quality blog posts and watching youtube videos?
Not saying it's better or worse, but I'm willing to say that the understanding you'll get from blogs is going to be be different than from a long-form book.
Books get the benefit of knowing where they left off one chapter, and picking it up on the next. Unless you're reading a long series of posts on the same blog (which, in the limit, approaches reading a book), reading blog posts will lack that continuity, and I find them inferior for building up a basic understanding of a topic. What blogs do really well, IMO, is for teaching you well-isolated techniques, or other such limited-scope ideas.
Your experience with C++ And Golang are in no way, shape or form comparable. If you've been doing C++ for 15 years, Golang is a comparatively small learning curve. You just need to pick up on a few syntactic differences and you'll be at that basic level of competence that books will give you, and you're ready for the single-topic, specialized learning that you'll get from blogs.
In general, once you know a few different languages and want to learn a new one, read the language spec or a good book on the language.
Good blog posts are an option, too, but those are hard to discriminate from bad ones, and run a greater risk of being incomplete (hm: here's and idea for a new product: a service that ranks blogs for accuracy, completeness and timeliness (K&R C is accurate and complete, but if you want to learn C now, it shouldn't be the only thing you read, and possibly not even a thing you read))
>Appendix: Listing every word used in the book in alphabetical order and on which pages each was mentioned.
That's the Index. The Appendix is where they list FTP and web sites that are long defunct, sample code for interfacing with a discontinued piece of hardware, and of course an ASCII table.
I'm with you 100% on this. To me blog posts and internet articles are really good for getting insight into a particular issue you're currently having, or a to be exposed to a bit of interesting trivia. I find books to be far superior if you want to maximize your knowledge ingestion for a given set of time.
I once tried to give somebody my C# 4.0 In a Nutshell book when I upgrade to the 5.0 book. "Why do I need that, I can just look at MSDN?". Hrmm.
MSDN has all of it, everything that should be documented. It is easy to get lost, not knowing what and how much should be taken first. The value of a book in such case is to have its author as your guide (as in a tutorial, if you will, but a little bit more than that).
Not saying it's better or worse, but I'm willing to say that the understanding you'll get from blogs is going to be be different than from a long-form book.
Books get the benefit of knowing where they left off one chapter, and picking it up on the next. Unless you're reading a long series of posts on the same blog (which, in the limit, approaches reading a book), reading blog posts will lack that continuity, and I find them inferior for building up a basic understanding of a topic. What blogs do really well, IMO, is for teaching you well-isolated techniques, or other such limited-scope ideas.
Your experience with C++ And Golang are in no way, shape or form comparable. If you've been doing C++ for 15 years, Golang is a comparatively small learning curve. You just need to pick up on a few syntactic differences and you'll be at that basic level of competence that books will give you, and you're ready for the single-topic, specialized learning that you'll get from blogs.