I barely recognize anyone on esDiscuss. Heck, I barely recognize JS on esDiscuss, everybody is writing Java OOP style it seems.
-
@yoshuawuyts@BrendanEich using prototype you trade the memory cost for an additional lookup which is likely going to be cached
@Vjeux @BrendanEich I tend to stay away from complex inheritance patterns, so I can't really comment on the benefits of classes vs prototype
-
-
@yoshuawuyts@BrendanEich using prototype you add an additional lookup of __proto__ but you define those methods only once per class -
@Vjeux@BrendanEich Isn't is so that with `extends` you copy the properties of the target rather than referencing them? - 2 more replies
New conversation -
-
-
@yoshuawuyts@BrendanEich even with no inheritance, if you create your methods inside of a closure then you create a copy for each instanceThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@yoshuawuyts@BrendanEich the class syntax just defines behavior, you can implement it using both closure and prototypeThanks. 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.