Hey reactive JS folks! I'm working to bring Observables to the web platform by reviving a @thedomstandard proposal that got some attention a while ago. @BenLesh and I would love your feedback, so check out if you want to do things like this soon:

I'm a one-foot-in/one-foot-out AI doomer, but I also think it's crucial we develop AI as rapidly as possible on US soil. Read my latest at

RT @htmx_org: from the official chrome blog: it's happening

We're shipping this in Chrome 133 (stable on Feb 4th)! Read more in our latest blog post: Huge thx to @nomsternom for help bringing this to life, partners & frameworks that helped test it, and the spec ecosystem for working with us to get it standardized!

RT @theo: The browser finally has a way to move elements. Yes, really. It took this long. Obv I had to make a video about it

@TechStackNation @BenLesh Let’s make it happen!

@LeaVerou @MattiasBuelens @luke_warlow Just changing the behavior of all of the core APIs out from under developers poses a compatibility risk though. Lots of this was discussed in

@nayte08 Citation needed:

@luke_warlow @isocroft @TC39 @wicg_ Oof I misread. I’m dumb! Thanks

@Keithamus @passle_ @jaffathecake Meh, not sure it'd need to be a static method, but yeah maybe that's how it'd shake out.

@fabiospampinato To ship something in @WHATWG, no implementer can have strong objections: To ship something related to events, non-browser JS environments are considered "implementers". So Node, Deno, etc., have a say, which is our intention. See

@fabiospampinato I wouldn't say it has nothing to do with the DOM. The unsubscription mechanism relies on cancelation primitives like Abort(Signal|Controller) which are DOM primitives whose TC39 counterparts never got traction over there. See

@fabiospampinato Hmm, well going through TC39 would still bring it to the web, no? So I don’t think standardization venue would change whether we generally get it or not.

@Keithamus @passle_ It can definitely work with overloads but yeah the question is: is it too awkward to justify using observe() like this polymorphically. @jaffathecake, thoughts?

@fabiospampinato My plan is absolutely to ship this API. Of course I haven’t gone through the launch process yet so while there is not approval right here and now, yeah I expect it to ship.

@robwormald @jaffathecake I like this one!

@oriSomething @rachelandrew button.subscribe('click').subscribe(e => console.log(e))? I don't think so!

RT @ThisDotMedia: @domfarolino @ladyleet

RT @ThisDotMedia: Observables: Coming to a Chrome Browser Near You! Hang out with @domfarolino and @ladyleet to learn about the impending…