@getify to make sure I am thinking of same thing you are, could you give example?
-
-
@wycats@brendaneich let's not pretend that the organic patterns that devs have grown to work-around JS quirks haven't restricted future JS. -
@getify@BrendanEich I have literally been the #1 advocate for considering existing patterns on TC39. It's not an absolute. -
@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? - 9 more replies
New conversation -
-
-
@getify@BrendanEich this is not about TC39 vs "some of us"; it's about giving syntax to a 20-year-old pattern that everyone uses -
@getify@BrendanEich syntax reduces cognitive overhead, which you can't just wish away. -
@wycats@brendaneich and see, you're arguing the "classes are better prototypes" path, which brendan earlier disclaimed.
End of conversation
New conversation -
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.