cloudflare - Is resource bundling needed on SPDY to reduce response times -

here use term bundling refer concatenate js , css resources reduce number of http requests. http/2 solves underlying issues gave birth resource bundling web development best practices in first places (round trip times, resource fetch blocking). however, how spdy, deployed, shares these characteristics http/2?

if use spdy-aware cdn, cloudflare, there sense bundle resources anymore if not need care legacy clients?

please note resource transpiling might done separately bundling , question response times, not compiling code.

http/2 (and predecessor spdy, being phased out) clients can perform larger number of concurrent requests server http/1.1 clients.

where http/1.1 between 4 , 8 concurrent requests @ time only, http/2 can typically 100.

the bundling of resources workaround http/1.1 limitation, , it's not strictly needed anymore http/2.

the reasons think of continue bundling may increase gzip compression efficiency of resources (but should measured quantify benefits - , small if @ all) or other application reasons.

if don't care legacy clients, in typical case can avoid bundling resources when using http/2 enabled cdn.

this should simplify build of web application (no need of bundling phase anymore) without losses in response times, way sure measure specific case.