It's always frustrating to see images go viral with no credit to the incredible photographers who take them. And it's happening with the National Guard at Capitol pics. So this remarkable image was captured by the AP's J. Scott Applewhite.
More from Government
NEW: the Georgia House Special Committee on Election Integrity is meeting at 3 this afternoon and just added HB 531 - a 48 page omnibus elections bill that proposes a *lot* of changes. #gapol
Here's the text:
First, it would ban county elections offices from receiving outside funding to run elections.
This, after CTCL and Schwarzenegger gave money to both D and R counties in 2020 to help with pandemic.
(although I wonder if the county gov't could take the grant, then disburse?)
Next, it outlines ways that poll workers can serve adjacent counties (currently, you can only work in your county of residence)
This section mirrors an SOS-backed bill from 2020 that would require more machines, more poll workers or splitting up precincts if a 2,000+ person precinct has lines of more than an hour.
More on that proposal: https://t.co/7BfIcrI81q
This is an anti-Fulton County mobile voting bus section
(although I still believe that it's using the wrong code section since the busses are for *early* voting and fall under 21-2-382)
Here's the text:
First, it would ban county elections offices from receiving outside funding to run elections.
This, after CTCL and Schwarzenegger gave money to both D and R counties in 2020 to help with pandemic.
(although I wonder if the county gov't could take the grant, then disburse?)
Next, it outlines ways that poll workers can serve adjacent counties (currently, you can only work in your county of residence)
This section mirrors an SOS-backed bill from 2020 that would require more machines, more poll workers or splitting up precincts if a 2,000+ person precinct has lines of more than an hour.
More on that proposal: https://t.co/7BfIcrI81q
This is an anti-Fulton County mobile voting bus section
(although I still believe that it's using the wrong code section since the busses are for *early* voting and fall under 21-2-382)
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.