@BrendanEich @mikemaccana No, no need to rock the boat.
-
-
Replying to @domenic
@domenic@brendaneich@mikemaccana i suspect it should be strongly reconsidered. We will be stuck with it for some time otherwise.1 reply 0 retweets 1 like -
Replying to @stefanpenner
@stefanpenner@BrendanEich@mikemaccana if you can convince@wycats then go for it but I don't want to awaken that dragon.3 replies 0 retweets 0 likes -
Replying to @domenic
@domenic@stefanpenner@mikemaccana@wycats 1/ Tiny dragon! Let's recap the argument to prepare: object literals make enumerable props so...1 reply 0 retweets 0 likes -
Replying to @BrendanEich
@domenic@stefanpenner@mikemaccana@wycats 2/ refactoring function C(){};C.prototype={m(){}} to class C{m(){}} should keep m enumerable.4 replies 0 retweets 0 likes -
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
@domenic @mulambda @BrendanEich @stefanpenner @mikemaccana We aren't going to have $el.autocomplete({ source(req, res) { ... }) not 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.