Open eeeps opened 6 years ago
Thanks for writing this up, @eeeps. I don’t know quite enough about the problem space to volunteer. (But can, if someone could partner with me!)
I did want to call this out, though:
My feeling is, any performance requirement we include should be from users’ or authors’ perspectives, not implementers’. We should write about the consequences of performance
This seems like a really, really key distinction to me, and +1 to hewing to it as we work on this requirement.
Everything that I read from people who understand the mechanics of layout leads me to believe that container queries are going to be necessarily more expensive than media queries, and potentially much more expensive.
Here’s a choice example from @dbaron (emphasis mine):
We should at least mention performance in the document. However, as I said in #7, I am wary of putting any particulars on this. My feeling is, any performance requirement we include should be from users’ or authors’ perspectives, not implementers’. We should write about the consequences of performance, – rather than writing from a hardcore Computer Science perspective, with an understanding of the problem from the inside, out (as @dbaron does above).
Ideas? Volunteers?