A modern programming language that makes developers happier.

kotlinlang

<https://www.youtube.com/watch?v=aW1iR0Mmitk|Design Patterns in Kotlin: Proxy and Decorator>

Design pattern need *not* apply?

Decorator/Proxy often introduce unnecessary wrapping and types
```val processor = LoginProcessor(
  Logger,
  CacheProcessor(
    Cache,
    RequestProcessor()
  )
)```
We can achieve the same effect without introducing these wrappers/types by simply using extension functions
```val processor = Processor()
  .log(Logger)
  .cache(Cache)```

Hi <@U019WDTQTS6>,
Using extension functions is a fine approach as well :slightly_smiling_face:

The pattern really breaks down and we are just left with extension functions :sweat_smile: 

only remaining vestigial is the names decorator and proxy 

Anyways, great work with the video :+1: really made me rethink this whole pattern for my presentation

<https://pl.kotl.in/t4R0DRmls> same idea but with only interfaces and extensions

Funny how we both came to the same solution without the decorator pattern :sweat_smile:

You could argue it’s still the decorate pattern, but without _explicit_ types :wink:

no wrapping though - which is good. This no longer resembles the original pattern from the GoF, therefore it is not decorator