| 11:54 | <littledan> | this is a good goal. It'd be good if you ask questions pushing towards this. |
| 11:54 | <littledan> | what I don't want is for people to say, "OK that means signals have to be DOM" since that would make no sense |
| 13:36 | <littledan> | jschoi: I encourage you to ask these sorts of questions |
| 13:36 | <littledan> | just keeping in mind avoiding those particular sorts of confusion |
| 15:38 | <jkup> | Really appreciate both of your comments and questions on this presentation! |
| 16:17 | <jschoi> | When littledan said he saw multiple ways to layer better with Observable and AbortController, e.g., integrating EventTarget as HTML integration on top of ES stuff, and the possibility of a new API that’s user-friendlier than AbortController, I got pretty excited. |
| 16:28 | <littledan> | Yeah it'd be great to work together on that! I think an upgraded AbortController would be an essential thing if we want interop between frameworks -- this is kind of orthogonal to signals, but everyone has a global which is the current disposal context, and nests these |
| 16:28 | <littledan> | this is my very rough gist about the topic, which I need to improve https://gist.github.com/littledan/47b4fe9cf9196abdcd53abee940e92df |