3 ms·
At a high level, it's because Atom is buult from components, and each of those components is made up of hundreds of components, and each of those is made from h
by phendrenad2 8y ago
At a high level, it's because Atom is buult from components, and each of those components is made up of hundreds of components, and each of those is made from hundreds of components, etc. Each component is general-purpose in some way, and includes code that isn't used by Atom. To be slightly more specific, when I pull apart components like this to figure out why they're so large (like a 100MB XML-parsing library), the vast majority of the bulk is usually huge tables of data, such as unicode mappings. Most likely, Atom contains multiple components which contain the same data tables, but because of the hierarchical nature of modern software development, no one can cut through the layers and DRY up (denormalize?) that data.
- insomniacity 8y agoRight, but isn't tree-shaking a thing now? Is it possible to do that with Electron apps?
- neilsimp1 8y agoI think developers probably tree-shake the HTML/CSS/JS that is running inside of Electron, but tree-shaking all of Chromium can't be the easiest thing to do. Not that I disagree with you, that should be a part of the Electron publishing/packaging step.