3 ms·
The old ones did this. Want to learn C? Read K&R. Want to learn Perl? Read the Camel book. Want to learn C++? Read Stroustrup. That was the way we learne
by AnimalMuppet 8y ago
The old ones did this. Want to learn C? Read K&R. Want to learn Perl? Read the Camel book. Want to learn C++? Read Stroustrup. That was the way we learned.
These days? Not so much. Stroustrup is now big enough to use in self-defense. I'm not sure there ever was an equivalent book for Java. (There is one for Go, however.) React? Angular? TypeScript? Do they have authoritative books? If they do, is that the canonical way to learn them?
I think something changed 20 years ago. The book used to be the way to learn, and now it's not. I don't know if the programmers changed, or if the languages changed, or if the books changed, but something did.
- JeremyBanks 8y agoFWIW Rust has "The Rust Book" as their primary long-form documentation, separate from their reference documentation. It's a common starting point for people new to the language. I read it in chunks as I was getting started. I'm not sure how it compares to those works of the past (perhaps less detailed?), but I found it much more approachable than most languages' documentation and more in-depth than most languages' tutorials. The old ways may not be entirely lost.
- steveklabnik 8y agoAll three of the books your parent mentions were explicit influences on TRPL. So yes, it lives on :)