@BrendanEich @wycats btw i don't think i'd call that throw future proofing. many have coded based on toString assumption to fork new vs call
@getify @BrendanEich you should gist the code you are saying broke.
-
-
@getify@BrendanEich ES5 code was allowed to throw in the constructor, and that was actually a quite common defense! -
@wycats 's decorator proposal I think shows the true power and benefit of class. *THAT*'s the biggie, for me at least.@getify@BrendanEich -
@adamrackis@wycats@brendaneich further reinforcement of my OP… decorators are distinctly "class-like" and alien to prototype-only patterns -
@getify@AdamRackis@BrendanEich what is a prototype-only pattern? -
@getify@AdamRackis@BrendanEich ES5 constructors quite often throw when called, just in weird ways. What makes you think otherwise? -
@wycats@adamrackis@brendaneich "what makes [me] think otherwise?" nothing more concrete than i've been around just as long as you. -
@getify@AdamRackis@BrendanEich you are making an empirical claim: ES5 constructors very rarely throw when [[Call]]ed. Self evidently false -
@getify@AdamRackis@BrendanEich http://this.foo = bar or http://this.foo in an ES5 strict constructor will throw 100%. - 6 more replies
New conversation -
-
-
@wycats@brendaneich i already did. as one distilled example: https://gist.github.com/getify/87ce0cbe4dc340b2bed8 …Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.