@domenic @stefanpenner @mikemaccana @wycats 1/ Tiny dragon! Let's recap the argument to prepare: object literals make enumerable props so...
-
-
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 -
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
@domenic@wycats@mulambda@stefanpenner@mikemaccana A proof: built-in class methods non-enum from the get-go. Yet want equiv self-hosting.1 reply 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@domenic@wycats@mulambda@stefanpenner@mikemaccana `class` is only syntax sugar? should behave the same. Adds to JS? diff +3 replies 0 retweets 0 likes
@pixnbits @BrendanEich @domenic @mulambda @stefanpenner @mikemaccana The question is what it's syntax sugar for. Could be sugar for non-enum
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.