@domenic @stefanpenner @mikemaccana @wycats 2/ refactoring function C(){};C.prototype={m(){}} to class C{m(){}} should keep m enumerable.
-
-
Replying to @BrendanEich
@domenic@stefanpenner@mikemaccana@wycats 3/ but refactoring equiv lost for constructor/super if used, & anyway usability/commonality win.4 replies 0 retweets 1 like -
Replying to @BrendanEich
@BrendanEich@domenic@stefanpenner@mikemaccana because $.extend({}, { foo() {} }) must copy!2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@BrendanEich@domenic@stefanpenner@mikemaccana but $.extend({}, class C{foo() {..}}) doesn't need to.3 replies 0 retweets 0 likes -
Replying to @mulambda
@mulambda@BrendanEich@domenic@stefanpenner@mikemaccana Others insisted on consistency, which forced my position.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@mulambda@BrendanEich@stefanpenner@mikemaccana I think consistency is preferable. object literal methods are more method than fn5 replies 0 retweets 0 likes -
Replying to @domenic
@domenic@wycats@mulambda@stefanpenner@mikemaccana A foolish consistency. Again, enum methods in pre-ES6 "classy" code = bug not feature.3 replies 0 retweets 2 likes -
Replying to @BrendanEich
@BrendanEich@wycats@mulambda@stefanpenner@mikemaccana right, so why encourage enum methods in object literals?2 replies 0 retweets 0 likes -
Replying to @domenic
@domenic@BrendanEich@mulambda@stefanpenner@mikemaccana And with real classes, they will be used even less for classy code.2 replies 0 retweets 2 likes -
Replying to @wycats
@wycats@BrendanEich@mulambda@stefanpenner@mikemaccana I think this is all wrong, but don't care enough to argue. Just, for the record.2 replies 1 retweet 1 like
@domenic @BrendanEich @mulambda @stefanpenner @mikemaccana Your position is that $el.autocomplete({ source(req, res) { .. }) shouldn't work?
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.