@jo_liss I’m generally +1 on that, but I do not think the majority of core would be.
/cc @stefanpenner
@stefanpenner For example, NOBODY uses Ember.Select and maybe we can move deprecated stuff into separate modules.
-
-
@fivetanley I think@wycats meant, no-one uses it without pain. :troll face: -
@stefanpenner@fivetanley what I meant was if we ship {{select}} we can get rid of Ember.Select from apps while leaving it in the codebase -
Tweet unavailable
-
@fivetanley@wycats@stefanpenner we’ve essentially got this https://gist.github.com/kselden/7758990 with some pretty small changes.
End of conversation
New conversation -
-
-
@wycats we have lots of head-room to reduce file-size (we should do so without trolling ergonomics or performance though) -
@wycats I feel pretty confident we can squeeze out another 6KB. Again, this is only a stepping stone for us. -
@stefanpenner without AMD that would have been a very valuable 6KB@wycats -
-
@stefanpenner@ebryn I just don't think that going from 60k to 80k is a an acceptable "stepping stone" -
@wycats confirm. this is unacceptable even as an intermediate thing@stefanpenner
End of conversation
New conversation -
-
-
@wycats are you serious?@stefanpennerThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wycats@stefanpenner Nobody uses Ember.Select? What else should we use? There’s no select component, right?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wycats@stefanpenner half my components extend Ember.SelectThanks. 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.