As far as I can tell from some inserted console.log()s, as the code currently stands in ui2, the frontscope re-downloads every single OEIS sequence on the list of "IDs of current interest" stored in the browser every single time the visitor
opens a new URL
uses the visualizer switcher
uses the sequence switcher
goes to a different specimen from the Gallery.
As the number of OEIS IDs on this list grows -- which it inevitably will for a repeat user, especially one that does not clear browser storage often -- this constant re-download becomes truly prohibitive. We need to devise a strategy for making at least some of these sequences very accessible without ultimately completely overwhelming the user interface.
I have at least in #420 moved these initializations to an explicit async function so we can control to some extent when this computational burden will happen.
As far as I can tell from some inserted console.log()s, as the code currently stands in ui2, the frontscope re-downloads every single OEIS sequence on the list of "IDs of current interest" stored in the browser every single time the visitor
As the number of OEIS IDs on this list grows -- which it inevitably will for a repeat user, especially one that does not clear browser storage often -- this constant re-download becomes truly prohibitive. We need to devise a strategy for making at least some of these sequences very accessible without ultimately completely overwhelming the user interface.