I like this one: "By definition, a program is an entity that is run by the computer. It talks directly to the CPU and the OS. Code that does not talk directly to the CPU and the OS, but is instead run by some other program that does talk directly to the CPU and the OS, is not a program; it's a script." Here's the other eleven.

There's an oft ignored fact that design patterns are really just missing features. Each and every single GoF design pattern is just a language feature. For example, the Command pattern is completely pointless if you have first class functions. Composite and Decorator are just recursive unions (of differing multiplicity.) Adapter, Bridge, and Facade are just use cases for composition.

I can do this all day, I did a semester project on cross-language implementation comparisons using design patterns as a goal.

I should probably mention that all languages have "design patterns," it's completely insane to include every single possible feature in a language (such that you'd have a feature for every macro-structure you can concieve of.)