but when codesplitting techniques are missing and the primary cost is in js parse + compile it leaves them in a perf hole.
-
-
if I think speaking positively about code splitting will cause users to switch away from ember, why wouldn't I 1/
-
instead argue defensively about the value of code splitting today. These are the (bad) choices we're given. 2/2
-
-
personally, i'd rather hear "yeah! we're working on it (https://github.com/emberjs/rfcs/pull/176 …)" than "stop weaponizing users"
@samccone@tomdale -
"the beatings will stop when morale improves"
-
and I'm sorry, but "frameworks are the problem" cannot be easily responded to via "we're working on it"
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.