Only the first user who hits a rarely used execution point may experience the noticeable latency, if he also has slow internet, etc. As soon as the user execut

Only the first user who hits a rarely used execution point may experience the noticeable latency, if he also has slow internet, etc. As soon as the user executes a rarely used function, the information is about this fact is sent to the server and it includes this function into the active set to be send to future users. In the video I manually initiate re-generation of the "active" and the "rest" scripts, but the most primitive MVP was supposed to schedule re-generation of the scripts when receiving info that some previously unseen functions are executed in browser. Obviously, if the idea is developed further, the first user's experience may also be improved - a spinner shown. Pre-loading the inactive set of functions in background may also be considered (pros: it allows to avoid latency for users ho invoke rare functionality, cons: we lose the savings of the traffic and browser memory and cpu for compiling the likely unneded code). (BTW, further development of the idea includes to splitting the code more granularity than just "active" / "inactive". E.g. active in the first 5 seconds after opening the page loaded immediately, likely to be active soon, active but rarely called - the later two these parts definitely need to be loaded in background)