[2:50]<Dantman> @_@ ahhh... trying to make a webm file is hard [12:43]<Wes-> Should the standard classes in various modules be referentially identical so that instanceof Array works when passing Arrays from one module to another? [12:43]<Wes-> Should they be different, so that modules adjusting prototypes do not affect other modules? [12:44]<Wes-> Does it matter enough to discuss? :) [12:47]<ondras> we already have this issue present; in cross-window scripting :) [13:43]<Wes-> ondras: Good observation! [14:55]<deanlandolt> Wes- it should be undefined because instanceof is *not* to be counted on (partly because of ondras' point :) [15:13]<WesMac> deanlandolt: *nod* - also, related to ondras' point, secure sandboxes [15:13]<WesMac> deanlandolt: But it raises an interesting question - we have, in the past, considered automagically extending String when require("binary") [15:13]<WesMac> (a practice, which, FWIW, I find horribly awful) [15:14]<WesMac> My preference is to require API users to explicitly intialize classes they want to extend, e.g. [15:14]<WesMac> require("binary").extend(String) [15:14]<WesMac> before using String.toByteString() [19:43]<WesMac> deanlandolt: Hey, I was planning to send my latest draft out to a couple of other people for peer review in a few minutes. Any chance you had a chance to cobble something together w.r.t. ES-5 shims? [19:43]<deanlandolt> yeah, it's just a list of shimmables pointing to the relevant sections in es5 [19:43]<deanlandolt> i'll send it to you in a sec [19:44]<WesMac> deanlandolt: Awesome, thanks! [19:46]<kixxauth> \q [20:40]<WesMac> deanlandolt: Thanks for the list, and especially taking the time to dig up the normative references [20:41]<WesMac> deanlandolt: Are Object.seal and freeze possible to implement with ES3? [20:41]<WesMac> (I didn't think they were) [22:30]<Wes-> Is there a non-sugary justification for the replacement of module exports? [22:31]<Wes-> Are there people who feel particularly passionate about the addition of "return exports"?