W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2018

Re: [csswg-drafts] [css-nesting] request to pick up the css-nesting proposal

From: Chris Eppstein via GitHub <sysbot+gh@w3.org>
Date: Fri, 15 Jun 2018 23:27:39 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-397766220-1529105258-sysbot+gh@w3.org>
@jonjohnjohnson As I understand it, it's not that it's a performance hit per se, it's just that none of the css parsers are built to handle arbitrary token look-aheads. So a spec that requires such a thing will get rejected.

In terms of performance, it will be interesting to benchmark the relative performance of precomputed nesting with compression vs an in-browser expansion with compression. The compression algorithms used by gzip and brotli do a good job with compressing duplicate idents in close proximity -- exactly the type that nesting produces, so precomputed nesting may turn out to be a performance benefit due to having only negligible impact on stylesheet transfer time after compression.

-- 
GitHub Notification of comment by chriseppstein
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2701#issuecomment-397766220 using your GitHub account
Received on Friday, 15 June 2018 23:27:41 UTC

This archive was generated by hypermail 2.3.1 : Friday, 15 June 2018 23:27:43 UTC