4 January 2020 @MAGAanalysis #OverturnGeorgia

I Listened To The Entire Interview...

And so should you! I'd rather it were just the interview itself, from NO news outlet, but when I checked at YouTube, it was only News channels' postings I could

More from Pasquale "Pat" Scopelliti

More from Politics

I told you they’d bring this up


I was wondering why that tweet had so many stupid replies. And now I see


Seriously, this was “the night before.” If you’re at the march where they’re changing “Jews will not replace us” and “Blood and soil,” you’re not a “very fine person.” Full stop.


There are 3 important moments in that transcript.

1.) When someone asked Trump about a statement *he had already made* about there being blame on “both sides,” he said the “fine people” line.


2. Trump does clarify! “I’m not talking about the neo-Nazis and white nationalists — because they should be condemned totally “

Okay!

Then adds that there were “many people in that group other than neo-Nazis and white nationalists.”

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.