Maybe they're actually booing because Hickenlooper is misrepresenting and hurting his opponents (and fellow Democrats), not because they actually want the things that he parodies?
(Sure, probably a few in the audience do want these things, but a small minority.)
"Safety is at risk." Plumbers calling on Texas Governor to call a special session after Legislature unexpectedly wiped out the agency that oversees them and the entire state plumbing code
texastribune.org/2019/05/28/…
I agree with your premises, but I also think many people overestimate the amount of shared understanding of how to convey tone in writing -- or perhaps underestimate the diversity of their readers in an online context.
For SF downtown, March-April-May normals have each month's normal rainfall about half the previous. May-June-July falls faster than that. (May 30 - June 10 is probably a factor of two on its own.)
Yes, the AMP HTML version shows slightly more context around the commented text, which seems like a UI improvement that ought to be in all versions... but that's not nearly enough to justify the doubling in size.
So Google Docs email notifications (about comments being resolved) have added an AMP HTML to their multipart/alternative package. The sizes of the three parts I just got:
text/plain 2.2 KB
text/x-amp-html 37 KB
text/html 18 KB
Shouldn't the AMP half be... smaller?
A graph of the current age of the US president over time (since Truman), and how the 2020 Democratic candidates [*] would fit into that graph if elected.
Source at github.com/dbaron/president-…
[*] candidates qualified for the debates
Actually, I think run-to-completion is the wrong phrase there, but I can't think of the right one for the idea that batching up of buffered changes isn't exposed through the API surface.
Sure, it's a new platform primitive, and one whose exposure to JS would break run-to-completion semantics, but which can be exposed to CSS.
Calling new platform primitives that you don't like "magic" doesn't seem helpful here.
That said, the layout ordering might actually be a little more interesting than that in that, with width-only containment, the style and layout of the subtree would need to run in the middle of the layout of its container.
Agreed.
And this does have performance overhead. But that overhead should be lower than the cost of doing a complete style and complete layout and then changing it in response to changes made in JS.
I think we could build container queries on top of CSS containment (need to separate layout-width & layout-height). That is, have container queries in stylesheets on elements with the right containment . Then able to container-query the width given contain:layout-width, etc.
Please reconsider.
SB 50 is critical to the growth & fairness of our economy and to reduce our effects on the environment and contribution to global warming.
*Starting* to fix California's housing crisis can't wait another year. Building will take many years after law passes.