Playbook: How it looks at the end
GOOD FRIDAY MORNING. Here’s how your American government is ending the year -- and the TRUMP presidency.
More from Jake Sherman
More from Trump
OK, #Squidigation fans, I think we need to talk about the new Wisconsin suit Donald Trump filed - personally - in Federal Court last night. The suit is (as usual) meritless. But it's meritless in new and disturbing ways. This thread will be
Not, I hope, Seth Abramson long. But will see.
I apologize in advance to my wife, who would very much prefer I be billing time (today's a light day, though) and to my assistant, to whom I owe some administrative stuff this will likely keep me from 😃
First, some background. Trump's suit essentially tries to Federalize the Wisconsin Supreme Court complaint his campaign filed, which we discussed here.
If you haven't already, go read that thread. I'm not going to be re-doing the same analysis, and I'm not going to be cross-linking to that discussion as we go. (Sorry, I like you guys, and I see this as public service, but there are limits)
Also, @5DollarFeminist has a good stand-alone thread analyzing the new Federal complaint - it's worth reading as well, though some of the analysis will overlap.
\U0001f6a8BREAKING: Trump files new federal court lawsuit in Wisconsin challenging the results of the election.https://t.co/LfKb2PUIkq
— Marc E. Elias (@marceelias) December 3, 2020
Not, I hope, Seth Abramson long. But will see.
I apologize in advance to my wife, who would very much prefer I be billing time (today's a light day, though) and to my assistant, to whom I owe some administrative stuff this will likely keep me from 😃
First, some background. Trump's suit essentially tries to Federalize the Wisconsin Supreme Court complaint his campaign filed, which we discussed here.
OK, #squidigation fans. This is a new Wisconsin case not filed by the Krake[n/d] team of Powell and Wood and NOT focusing on wild conspiracy theories. It's a competent and professional filing that raises things that would be real issues ... if you don't understand why they aren't https://t.co/ETvUiWV5du
— Akiva Cohen (@AkivaMCohen) December 1, 2020
If you haven't already, go read that thread. I'm not going to be re-doing the same analysis, and I'm not going to be cross-linking to that discussion as we go. (Sorry, I like you guys, and I see this as public service, but there are limits)
Also, @5DollarFeminist has a good stand-alone thread analyzing the new Federal complaint - it's worth reading as well, though some of the analysis will overlap.
Every one of these Trump election suits is the same gobbledygook garbage barge:
— Liz Dye (@5DollarFeminist) December 3, 2020
FRAUD!
It coulda happened.
Well, no, we can't prove it.
But just to be safe, best let the gerrymandered legislature give us all the electoral votes!https://t.co/Z926668H05 pic.twitter.com/xGZsJKIO7Y
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.