Chapter 13: Complexity

This chapter reiterates some concepts that are intuitive to most people
in the field. Things related to how we define complexity, from the
viewer's eyes. Be it programmers, end-users, or via static analysis.
We also see the usual categorization of types of complexity: essential,
optional, accidental.

We're then visiting the classic editor war and bringing the question of
which feature editors should have (or not).

Chapter 14. Languages

Personally, this chapter wasn't something new to me, but I'd definitely
recommend it to people that have stiff ideologies about their programming
language usage.

Quote:Warning: Choice of application language is one of the archetypal religious
issues in the Internet/Unix world.

Quote:To apply the Unix philosophy effectively, you'll need to have more than
just C in your toolkit.

> Why not C?

The answer, as with a lot of things in the book isn't a clear yes or no
but a case by case, a more in-depth discussion than thought-terminating
clichés.

Here the author emphasize, yet again, the concept of human-first approach
and whether C will fill it or not.
I also realized I've used all the languages listed in the
evaluation... that's interesting. But I think today there would need to
be an update that includes languages such as Go, Rust, NodeJS, etc..