I think GoF is all right, when viewed as a book of gadgets. That is, if you have this problem, then consider this mechanism as a fix.
The problem is, people treat it like a "here's how to do OO design" book. It is not suited to that, and especially not suited to being the one and only OO design book that people read.
I guess this is my actual problem with it, or at least the way that it's been received. It implicitly posits that programming is a collection of gadgets. A gadget is a fine thing, when you have decided _what_ you want to do and are looking for a way to do it.
But a gadget-centric process, whether is patterns or microservices, constrains the design space to assemblies. and that a really small and clunky part of the space.
The problem is, people treat it like a "here's how to do OO design" book. It is not suited to that, and especially not suited to being the one and only OO design book that people read.