I barely recognize anyone on esDiscuss. Heck, I barely recognize JS on esDiscuss, everybody is writing Java OOP style it seems.
-
@yoshuawuyts@BrendanEich at fb we used to write classes the pure js way by creating a fn and them mutating the prototype directly
@Vjeux @BrendanEich Similar to this? Was curious why you chose to not do that, could you enlighten me? -- https://gist.github.com/yoshuawuyts/1df67cf3feb5816728e8 …
-
-
@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 - 4 more replies
New conversation -
-
-
@yoshuawuyts@BrendanEich react is a different beast, it supports mixins with special merging for getInitialState, typing for propsThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@yoshuawuyts@BrendanEich here's the before after https://gist.github.com/vjeux/ca5c28098c3c8f394938 …Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@yoshuawuyts@BrendanEich it's now written how you want it written and prototype, like vtable in C++, is just an implementation detailThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@yoshuawuyts@BrendanEich also this pattern is likely going to allocate memory for every single method per instance.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.