3 ms·
> The ACM SIGPLAN talk is a very good starting place to get an understanding what he is talking about. What's the big difference from just using composition li
by magicalhippo 4y ago
> The ACM SIGPLAN talk is a very good starting place to get an understanding what he is talking about.
What's the big difference from just using composition like we've done for ages?
I mean, his examples in that talk was very reminiscent of stuff I've been doing for many years, and I don't consider myself to be special in any way. Writing decent interfaces, write useful implementations, then compose them together.
Not trying to be dismissive, I just feel like I'm clearly missing something as it's a bit underwhelming for a 2019 talk to be all about "composition is great, use it".
- metapsj 4y agoimho the key concept is in-process rest as in representational state transfer as an interface. instead of an imperative interface it's more of a protocol based interface. think http middleware built around a standard interface like ruby's rack, asp.net's owin, or python's wsgi. once you have that style of abstraction it becomes pluggable and you can chain them together. here's a past discussion on in-process rest. https://news.ycombinator.com/item?id=21560626 https://news.ycombinator.com/item?id=21560626
- magicalhippo 4y agoThanks, that's a bit more specific. Think I'd have to play with it to see how it really differed from my normal composition of interfaces and implementations.