While it's a great book to learn C with - easy to follow and just the right length for an introductory book - I'd say it's more of an (software) Engineering book than a (computer) Science book.

I thought it was wildly agreed that it's a pretty terrible book to learn modern C with?

It is however in other respects a fantastic example of great technical writing and a great text book.

But as I understand it it's today mostly an extraordinarily great book on inflicting legwounds on yourself.

K&R C is a minimalist introduction to the C language. And I love it for that.

The book does not try to forewarn you of the myriad pitfalls inherent in C code. Nor does it delve into the language's extended API available via a plethora of internal and external libraries.

What the book does do in only 228 pages is get you up and operational in C as quickly as possible. Then caveat coder.

Personally, I'd like to see more minimalist CS books. I'm tired of having to surf through introductory tomes that often exceed 1000 pages. I'd rather an intro book introduce me to its concepts in as few pages as possible and put the programming advice and copious reference materials elsewhere, like online.

It is. But I wonder if, when people say "CS", they really mean "Software Engineering". Of people who get a CS degree, I'd guess that 95% of them are going to work as Software Engineers rather than as Computer Scientists.

So: Yes, it's more an engineering book. Is that what michalu actually wanted, but didn't know to ask for by the right name?