Also just published a new version of my book removing all mentions to prototype extensions.
@stefanpenner @fivetanley @chancancode @abuiles I think it depends.
-
-
@wycats@stefanpenner@fivetanley@chancancode@abuiles very easy to end up with super long fn doing lots of varying things elsewise -
@wycats@stefanpenner@fivetanley@chancancode@abuiles which is harder to test and harder to maintain. -
@runspired split it into multiple methods?@wycats@fivetanley@chancancode@abuiles -
@stefanpenner@wycats@fivetanley@chancancode@abuiles that's the point of why I think evented is better, easier to split up -
@runspired@wycats@fivetanley@chancancode@abuiles its also obvious now to unit test didInsertElement in super.js (but not in event.js) -
@runspired i personally prefer "just functions" to using other concepts.@wycats@fivetanley@chancancode@abuiles -
@runspired I might even be convinced that app code should be allowed to do this@wycats@fivetanley@chancancode@abuiles - 17 more replies
New conversation -
-
-
@wycats@stefanpenner@fivetanley@chancancode@abuiles 2cents: often have many fns awaiting onDidInsertElement, keeps behavior encapsulatedThanks. 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.