I didn't find it clunky at all, and it's not about LINQ specifically either. It's about how you'd derive the Rx event-stream paradigm from the building blocks that were well-known circa 2012 when the article was written, and how it abstracts over things so seemingly different as mouse clicks and relational databases. It's supposed to give you insight instead of just telling how to apply X to do Y. However I'm already very familiar with the pattern and also know how it was derived using duality, so YMMV.
Can you speak to how useful you've found the pattern/paradigm? Sort of an ambiguous question, but I've sat through some intro Rx stuff at Microsoft seminars and I've yet to deliberately reference it when writing code. This isn't to say it's without merit, I'm just looking for inspiration.
Edit: Further clarification - I think I'm unfairly generalizing this to a mix between coroutines and an Observer pattern.
Erik Meijer is hilarious and brilliant in equal parts. I haven't read the article (added to my "things to read after work" pile) but I'd always be wary of taking anything he produces too seriously, or not seriously enough!
9 comments
[ 3.6 ms ] story [ 25.2 ms ] threadEdit: Further clarification - I think I'm unfairly generalizing this to a mix between coroutines and an Observer pattern.
https://philosophynow.org/issues/124/Is_Everything_A_Compute...