Re: [whatwg/dom] Improving ergonomics of events with Observable (#544)

For what it's worth I disagree with:

> Ironically, benjamingr , a LONG time supporter of RxJS may have killed any chance the community had at getting Observable on a platform when he added { signal } to addEventListener.

I acknowledge it covers one thing observables did better than EventTarget (and we absolutely _should_ keep improving EventTarget), but it doesn't really compare I think?

You can't `map` events with EventTarget (you can however wrap them in an async iterator and `.map` that). When you have synchronous events that matter (like a trusted user event triggering opening a window - where it has to be synchronous) - you can't use async iterators (micro-tick scheduling) and the semantics are clearly push based. Like you said - nothing composes, this has always been the bigger deal for me.

The thing that has been blocking observables to my knowledge for the last few years is that they were not presented to the committee and concerns raised and research did not progress because no one is funding it. I don't expect you to spend another 1000 hours for free on this, but let's remember we can still have observables in JavaScript if someone funds the work to do it or does it. I think WhatWG's and TC39's concerns can be addressed to everyone's happiness.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/544#issuecomment-1437561598
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/issues/544/1437561598@github.com>