Object oriented design patterns in the Linux kernel (2011) (opens in new tab)

Nice!

A pretty good paper to point people to when they mouth inanities like "OOD/OOP are bad-ideas/dead" etc. This sort of negative cargo-culting has now gotten so out of hand that you have new programmers today not wanting to learn classic OO design/techniques. They merely parrot what they had read somewhere (usually some abuse of OO inheritance techniques) without thinking/learning for themselves and thus throw the "baby out with the bathwater". The OO paradigm has been the single most effective imperative model for "programming-in-the-large" which has directly led to explosion in the software industry as it is today.

If anyone read this in detail: does it bring up cases that OO covers better than other ways of interoperability/interfaces in statically typed systems, eg Go's structural typing or fanciel module systems (eg Ocaml)?

Though it also talks about dynamic systems like Smalltalk and GTK+, not sure if the comparison should be to statically typed languages.