- From: François REMY <francois.remy.dev@outlook.com>
- Date: Fri, 12 Jul 2013 18:36:34 +0200
- To: Sylvain Galineau <galineau@adobe.com>
- CC: "www-style@w3.org" <www-style@w3.org>
> Of course people will trade some perf for convenience. jQuery and other > frameworks prove this. But it's easy to overestimate how far that > trade-off can go. > > Anyway. This discussion remains highly speculative. It's still not so > clear what it is we're trying to optimize. 'Slow selectors' is just too > broad a target. I'd rather figure out where to go based on some real-world > experience of slow selectors. If these are so useful we'll soon have > actual qSA data to build a real plan on, instead of wobbly piles of nested > interlocking assumptions. I'm personally okay waiting for more usage information. By the time browsers support the 'complete' profile, I'm quite confident good polyfills will allow to fill the 'stylesheet/qSA' gap in a way that will be acceptably convenient for authors. Based on those js solutions, we will probably be able learn a lot more about what people care about and which trade-offs they use. Still, I think this discussion was useful in the sense it helps understanding the issues and optimizations in place, and can be used as a reference for qSL polyfill writers.
Received on Friday, 12 July 2013 16:37:01 UTC