- From: Brendan Eich <brendan@secure.meer.net>
- Date: Tue, 10 Mar 2015 14:18:51 -0700
- To: Jason Orendorff <jason.orendorff@gmail.com>
- CC: Jonas Sicking <jonas@sicking.cc>, "Mark S. Miller" <erights@google.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, David Dorwin <ddorwin@google.com>, public-script-coord <public-script-coord@w3.org>, Boris Zbarsky <bzbarsky@mit.edu>
Jason Orendorff wrote: > So the spec has a way to say "ok, create a bunch of objects and hook > 'em up like so", but scripts don't. A bit of "putting magic into the > API" seems unavoidable to me, as this is exactly the property you're > after, right? And as Mark showed, with ES6 the magic can be self-hosted -- but specs should not over-specify like that, at least not without a lot of care to avoid observables we don't want to specify (now or in future; as Tab reminds everyone, future JS standards own some map and set primitives to workalikes and extensions). /be
Received on Tuesday, 10 March 2015 21:19:26 UTC