“I just don't know why there aren't uprisings all over this country. Maybe there should be.” — US House Speaker Nancy Pelosi (D)
“There will be blood in the streets” — USAG Loretta Lynch (D)
“Show me where it says that protests must be polite and peaceful.” — CNN's Chris Cuomo
“There needs to be unrest in the streets” — US Rep Ayanna Pressley (D)
“I just don't know why there aren't uprisings all over this country. Maybe there should be.” — US House Speaker Nancy Pelosi (D)
“I will go and take Trump out tonight.” — US Rep Maxine Waters (D)
“How do you resist the temptation to run up and wring her neck?” — MSNBC's Nicole Wallace on White House Press Secretary Sarah Sanders
“If we were in high school I'd take him behind the gym and beat the hell of of him.” — Democrat Candidate Joe Biden on President Trump
“Where is John Wilkes Booth when you need him” — Carole Cook
“They're still gonna have to go out and put a bullet in Donald Trump, and that's a fact.” — Rick Wilson, Dem Political Strategist
More from Government
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.