- From: Duarte Cunha Leão <notifications@github.com>
- Date: Thu, 14 Dec 2017 06:01:49 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/dom/issues/544/351718686@github.com>
@jhusain > Due to the failure of the TC39 CancelToken proposal, the web has a standardized cancellation primitive (AbortController) and JavaScript does not. At least one implementer has already expressed concerns about adding an additional cancellation primitive to the language and consequently to the web platform. That's what happens when the Web platform goes ahead and defines things not harmonized with TC39 — it ends up impeding TC39 from, eventually, doing it right (the way they would have wanted to or that ultimately would be best for the web). The same will happen, imo, with `Observable` if you pursue with this effort independently of TC39 — _observables_ have too many connections with the concepts of _events_, _promises_ and _async_ to not be tightly integrated with the design of a language. I also perceive, somewhat, by what I read in this thread, that it is your (of many of you) opinion that the friction and inertia of TC39 is unwarranted. I happen to see it as a great filter and guarantee that things aren't standardized unless they have met/satisfied all technical interests, and maybe even some political ones. Convincing people, fine tuning designs takes time, after all — I think that this is inevitable. It is taking long, most probably, because it is such a hard problem, in many dimensions (not just, technically, as the standalone API). Just like classes and modules did take long to settle on, and are very hard problems; despite all the difficulties, TC39 finally reached a consensus. The latter are more obviously language features, but, for me, events, and its thin connection with observables are also obvious language features. This is independent of whether these end up having any special syntax. It is true, imo, even if the result is a bunch of standardized interfaces that every API then seamlessly uses. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/544#issuecomment-351718686
Received on Thursday, 14 December 2017 14:02:36 UTC