I'm kind of surprised I haven't seen an article in @FiveThirtyEight or somewhere similar using the Total Survey Error framework as a tool for categorizing potential sources of survey error and tests for those hypotheses as election results get finalized.
It's tricky to test for, because surveys aren't asking about trust and we don't have great national benchmarks either. That said ...
More from Politics
So let's see a show of hands: how many of you even knew Huber was digging into the Clinton Foundation? While he was assisting Horowitz in his digging into the FISC/Steele Dossier/Fusion GPS/Perkins Coie/DNC/Hillary campaign stuff?
I'm sure Huber is coming to DC *only* to discuss Clinton Foundation things with Meadows and his committee.
He for certain, like, won't be huddling with Horowitz or that new guy, Whitaker while he's in town. That would NEVER HAPPEN. [wink wink wink!] 😉
I just spent a year and a half telling you they will SHOW YOU what they are REALLY DOING when they are READY.
Not before.
No matter how much whining is done about it.
I'm exhausted but it's worth it.
Now you know why they're f**king TERRIFIED of Whitaker, the closer tapped by Trump to come in late for the hysterical fireworks that will ensue soon.
Look who's suddenly fund raising for his legal defen- er, I mean, ha ha - his reelection campaign!
Breaking News: House GOP to hold investigative hearing into DOJ\u2019s handling of Clinton Foundation probe. Top prosecutor to be summoned. https://t.co/HogyXHHcvo
— John Solomon (@jsolomonReports) November 21, 2018
I'm sure Huber is coming to DC *only* to discuss Clinton Foundation things with Meadows and his committee.
He for certain, like, won't be huddling with Horowitz or that new guy, Whitaker while he's in town. That would NEVER HAPPEN. [wink wink wink!] 😉
I just spent a year and a half telling you they will SHOW YOU what they are REALLY DOING when they are READY.
Not before.
No matter how much whining is done about it.
I'm exhausted but it's worth it.
Now you know why they're f**king TERRIFIED of Whitaker, the closer tapped by Trump to come in late for the hysterical fireworks that will ensue soon.
Look who's suddenly fund raising for his legal defen- er, I mean, ha ha - his reelection campaign!
President Trump just attacked Adam on Twitter with his most profane insult yet. Will you chip in $5 to send Trump a message and show him you stand with Adam?
— Adam Schiff (@AdamSchiff) November 19, 2018
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.