joaquimrocha
commented
11 months ago IMO there's value in not downloading all the plugins' code right away, since we may not want to load some plugins anyway. However, what you are proposing makes does indeed make sense when we know we will load (or very likely load) the plugins. That's the case when with the in-cluster/web versions + shipped plugins.
Currently all Headlamp JS needs to download, and start executing, and then /config needs to be downloaded from the backend... and finally plugins are loaded. This can be a significant time (5-10 seconds), so a plugin may not even start downloading until then.
It would be better if plugin JS code could be downloaded right at the beginning of page load. This would decrease the overall time for the page to load and the plugins to run.