4 ms·
Why does everyone always suggest K&R? I really don't see the big deal. It's short, contains only trivial toy examples with no real world application, and touche
by aphextron 7y ago
Why does everyone always suggest K&R? I really don't see the big deal. It's short, contains only trivial toy examples with no real world application, and touches almost nothing on actual project architecture or best practices. I bought it expecting to learn to write programs in C but it's really just a reference manual on syntax.
- Timpy 7y ago> It is all you need to know about C…for the first few weeks. It seems the author was aware of this. Isn't syntax a good place to start for a new language?
- fabiensanglard 7y agoIn short: It is a great starter. The book is so tiny it won't discourage people and get them going in no time.
- aikah 7y ago> Why does everyone always suggest K&R? Because it's the best no bullshit book to learn C, period. Especially coming from garbage collected languages. It's not going to teach you valgrind or GDB, or even compile and link C programs but it will certainly teach you how to write C programs. > only trivial toy examples with no real world application Re-implementing POSIX commands is writing real world applications. > and touches almost nothing on actual project architecture or best practices. On what platform? Linux? Windows? Mac? tool chains are so different on all these platforms that it wouldn't make sense to spend time on that. That books is about C, not learning autotools and other horrors.
- globular-toast 7y ago> trivial toy examples with no real world application It teaches you how to write malloc. Plenty of the examples have real world applications. If you want a book on architecture then get a book on architecture. K&R is about C.