Moonchild wrote:So, the preloader will have limited use - loading and initializing extensions is what usually takes the most time.
But, I guess if you chop a relatively long wait up in two chunks, it makes both of those waits matter less.
You should rename it "core preloader" or something?
No arguments there. I actually am not seeing a drastic improvement, with my many tabs and many extensions. Sure it might go from ~10s to ~7s now, but... anything over ~2s already interrupts my flow and once I'm in for a wait, another second or so hardly matters. I'm not sure if cutting off a negligible amount of time is worth having an extra process sitting in my RAM/tray 24/7 (I'm obsessive compulsive about that sort of thing).
I'm really just doing this as a learning experience, and because others seem happy with their results.
But yes, I think the idea behind this preloader(coreloader? softloader?) is keeping it ready to start *at all times*, so that the user may open and close it as often as he/she wishes and would perceive a reduced browser load time.
For me, I'm going to create an AHK script that fully loads the user session + extension, hidden, whenever the process exits (with a delay so it doesn't interfere with restarts). Then unhide the window when the title string changes (user clicked a url somewhere, or a shortcut that opens a newtab) If it works well, I'll post it here, or in the thread I may make for the preloader.