SebastianVerified account

It's dowright amazing how much you can fit into 100k min+gzipped if you start with a minimalist toolkit and you're conscious about size the whole time.

Absolute. We got first interaction of http://squoosh.app  down to 15k, and it wasn't particularly hard. I went into that project thinking I'd find some empathy for folks who ship 600k bundles, but I'm more convinced it's just careless.

I would like to see how y'all can upstream your process and tooling to the larger community. I think it is unrealistic to expect reaching the sub 100kb bar to be a normal thing for 99% of developers. The only way this will happen is if our frameworks+tools do this by default.

I do not want to drag your accomplishments through the mud, I want to be realistic when communicating. Most applications I work on and see have 1+ frameworks, 1+ UI toolkit libs, and 1+ "heavy" 3rd party lib. Under 100kb is just not possible with today's frameworks+toolkits

I have a feeling in the coming years the long tail will be getting all of the third-party libraries people use to be more tree shakable and tiny. TMK, every framework team is working very hard at build time optimizations to make bundles very small in coming releases.

I wish TypeScript was able to eliminate unused methods. It feels really well placed to do that.

(and minify private methods/property names)

You should checkout tsickle it enables this exact thing! It's another nice example of Google providing robust JavaScript tools to the community.