Pablo-WMDE added a comment.
> init.js ... Why do we send it through Babel etc. at all? > trading some development convenience for a drastic reduction in script size. We should be able to find a configuration that works for us, instead of us working around the tool chain we picked to help us. > Can we change the order in which the initial modules are loaded? I share your skepticism about that option. > **we can start that load [of app], but then immediately add our event handlers** **Agree** > **reduce the size of the init module** The most effective way of doing this in my eyes would be to reconsider what are "app services". **Instead of passing a ready-made service container into app we could construct it inside of it**, passing it only (based on an interface not adding compile size) what is needed to do so (e.g. a ForeignApi). As a consequence, the concrete repo implementation would all move into app without sacrificing any conceptual clarity. What do you think? > I’m still very tempted to rewrite it in plain JS team discussions/decisions are a thing > dispatcher into a separate [3rd] module By definition the sum of modules can not be smaller than before. Rather each module carries its own copy of compatibility features and the sum is hence bigger. When ever links are detected, both dispatcher and app would be needed - never only one. What would we gain? --------- Is there a majority to create tickets for the two bold statements (pun intended)? TASK DETAIL https://phabricator.wikimedia.org/T233305 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Lucas_Werkmeister_WMDE, Pablo-WMDE Cc: Pablo-WMDE, Lucas_Werkmeister_WMDE, Michael, Aklapper, Lydia_Pintscher, darthmon_wmde, DannyS712, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, _jensen, rosalieper, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
