What does that even mean ..? Is that like every pixel width/height combination from 200 to <size of your desktop> ? .. If so, that's a lot of CSS. If not, you won't get the current responsiveness you see when you resize your browser on a responsive website.

It just means precalculate a small number of fixed screen sizes.

So portable devices, and maximized desktop browsers would benefit, as they have regular dimensions.

I imagine they would precalculate the constraint "solutions" in the variables used inside the solver. GSS would still be supplied, and would still need to translate the solver variable values to CSS style values.

This way, if the window resizes, or has an initial size that is not precalculated, it can still be accommodated.

GSS author here. What we're working on is a lot crazier than that! Using phantom.js we precompute layout for every possible screen size & generate pure CSS.

Precomputation - From small phones to large desktop, there are ~2million width & height combinations, even if solving a single screen size takes 10ms, were talking ~6hours. To get around this, using a sort of bisection method, we selectively solve for as few screen sizes as possible to test linearity of each variable's solved values. With Cassowary each variable is linear between breakpoints, making this possible.

Pure CSS Generation - Generate media queries & styles with calc() where calc is a linear function with respect to vw & vh units. A little JS we only be needed for browsers that don't support calc or viewport units.

Limitations - Precomputation will only work for deterministic / static layouts. For a highly volatile DOM, runtime will be needed, but that's probably OK given the fact that you're already using JS to mutate things in runtime.