No BoilerplateMay 17, 2024

"A modern developer need not know the Gang of Four "Design Patterns",
but they should at least have forgotten them."

Agree? 🤔

 boost appreciated, let's find out!

Yep, still relevant
34.7%
No, it's not 1994
35.5%
The what patterns? (see replies)
29.8%
Poll ended at .
Show thread No Boilerplate
This freakin' book https://en.wikipedia.org/wiki/Design_Patterns
Design Patterns - Wikipedia

May 17, 2024 at 12:13pmWeb
Show thread No BoilerplateMay 17, 2024

It's got names you'll recognise:

  • Factory
  • Adapter
  • Proxy
  • Singleton

etc

But was designed for a C++/Java/Smalltalk world.

IMO, if your language has first-class functions and closures, you don't really need them...

Show threadApoqueMay 17, 2024

@noboilerplate Yeah, I agree Factory is by far the worst. It's just a `fn() -> impl T`/`Supplier<? extends T>`

That's one thing that Java 8 really rubbed in my face. There were _SO_ many single-function interfaces that I replaced/deleted with closures.

Show threadJaycieMay 18, 2024
@noboilerplate Hell yes! Hung a lampshade on this when xe were contributing to the CoffeeScript Cookbook.
Show threadViiriMay 25, 2024
@noboilerplate I would argue further that it was designed for “classic” C++. We have C++20 now and most of these are obsolete in that context. Modern C++ has design patterns all of its own.
Show threadJacketMay 17, 2024
@noboilerplate Interestingly, the method factory is pretty much what rust implemented as traits. I think at least some design patterns can be used by programing language designers as feature needs.