What CSS minifiers also leave behind

Re:What CSS minifiers also leave behind by mifreewil on Wednesday April 05, 2017 @05:11AM (#14040769)

Number of HTTP requests is not a concern with HTTP2 server push and multiplexing. In fact it's usually better to have 2 fairly sized files that can be downloaded in parallel rather than 1 large file.

[ Parent | on HN ]

Re:What CSS minifiers also leave behind by merb on Wednesday April 05, 2017 @05:50AM (#14040917)

probably not true, since most http/2 implementations that I know of use time multiplexing, which means that only one element at a time can pass, so the time is exactly the same.

I mean if I split a file in 10 exact pieces or if I split two files in the exact same 10 pieces as well I still have the same data.

(Edit: Well basically two files have mostly more data since they both might contain a BOM or so)

[ Parent | on HN ]

Re:What CSS minifiers also leave behind by mifreewil on Wednesday April 05, 2017 @01:38PM (#14043907)

There is a nice diagram here showing how requests/responses are able to be sent in parallel (not time-based multiplexing): https://developers.google.com/web/fundamentals/performance/h...

And see Nginx's `http2_max_concurrent_streams` option: https://nginx.org/en/docs/http/ngx_http_v2_module.html#http2...

[ Parent | on HN ]