On Fri, Jan 21, 2011 at 6:09 AM, Wes Garland <[email protected]> wrote: > On Thu, Jan 20, 2011 at 8:25 PM, Brendan Eich <[email protected]> wrote: > >> This is the killer for me. Do not want to change === and require all-paths >> runtime test coverage to migrate code into Harmony. >> > > You're bang-on about the end user impact of this change - I would not be > able to migrate any ES5 code to Harmony without full-on testing (not just > automated regression tests), meaning Harmony uptake would be slowed, > particularly in environments like mine where it is most cost effective to > pick a language version and use it across all platforms (we are heavily > invested in ES, and not just on the browser). >
No argument. In further discussion at the meeting, we also jointly concluded not to change === and to stick with a separate new eqal operation, spelling and syntax to be decided. > > Changing the semantics of an existing language feature smarts: I got bit > pretty hard as a relatively new JS developer with JavaScript 1.2 and am > still wincing. Of course, this is a much smaller change, but we have much > more code nowadays.. :) > > Wes > > -- > Wesley W. Garland > Director, Product Development > PageMail, Inc. > +1 613 542 2787 <tel:+16135422787> x 102 > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > > -- Cheers, --MarkM
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
