> The GUI-oriented 90's vibe, meaning zero examples that anybody would ever bother learning.
It was written in the 90's. GUIs were what application developers did back then. Web apps didn't exist yet.
> The bizarre stuff nobody ever uses (Flyweight? Bridge?).
If you've used enums in Java or instanced rendering in a game, you're effectively using Flyweight.
> Singleton -- 'nuff said.
They caution really hard against overuse of Singleton in the book, but all of those C programmers being dragged into OOP didn't know where else to stuff all their global state so they went to town on it.
> Factory, which favors opaque, magical return-type polymorphism.
If your language doesn't have first-class classes, Factory is really handy. If it does have first-class classes, well that means you basically have the Factory pattern in your language. :)
> Visitor, which is a solution in search of a problem
The day you write a compiler in an OOP language is the day you realize how unbelievably, amazingly, incredibly useful Visitor is.
It was written in the 90's. GUIs were what application developers did back then. Web apps didn't exist yet.
> The bizarre stuff nobody ever uses (Flyweight? Bridge?).
If you've used enums in Java or instanced rendering in a game, you're effectively using Flyweight.
> Singleton -- 'nuff said.
They caution really hard against overuse of Singleton in the book, but all of those C programmers being dragged into OOP didn't know where else to stuff all their global state so they went to town on it.
> Factory, which favors opaque, magical return-type polymorphism.
If your language doesn't have first-class classes, Factory is really handy. If it does have first-class classes, well that means you basically have the Factory pattern in your language. :)
> Visitor, which is a solution in search of a problem
The day you write a compiler in an OOP language is the day you realize how unbelievably, amazingly, incredibly useful Visitor is.