Thanks for your kind words. It’s always encouraging to hear positive feedback.
The blog post we’re publishing soon should clarify this, but at a high level, the primary obstacle is the fact that you can only have a single snapshot for the entire application. Also, the environment in which snapshots are generated doesn’t have access to browser globals or Node APIs, meaning some care needs to be taken to generate them. It’s not something we could just run automatically on all packages.
No promises about shipping this any time soon, but what might be possible would be the following: Allow package authors to specify a snapshot script for their package. This would be generated via a tool like electron-link that concatenates scripts together. Then we could expose some sort of command that would re-run the snapshot phase of the build process, but include snapshot scripts from third party packages. This snapshot could then be stored into the application bundle.
Making this work smoothly across all environments and machine configurations would probably be pretty challenging, but in theory it should be possible. It could even be something we ran in the background when we detected packages with snapshot scripts.
For now, however, I think it’s more fruitful for us to focus on reducing the overhead of Atom itself and the bundled packages as much as possible.