TL;DR, from what I can tell: Dropbox was using a JS bundler that didn’t support code-splitting or tree-shaking (y’know, the staples of modern JS bundling) and swapped to one that does. Not that there aren’t plenty sub-optimal components in code I work on, at home and at work, but there’s nothing revolutionary going on here.
TL;DR, from what I can tell: Dropbox was using a JS bundler that didn’t support code-splitting or tree-shaking (y’know, the staples of modern JS bundling) and swapped to one that does. Not that there aren’t plenty sub-optimal components in code I work on, at home and at work, but there’s nothing revolutionary going on here.