Pots of honey 🍯 are just pots of money 💰 https://t.co/XhS3wNM1Fj
New York Times Continues Swalwell Blackout Exposing Relationship With Chinese Spyhttps://t.co/NdkGtqLEiK
— \u200e \U00010912\u200eRabitt \u270c\ufe0f\U0001f1fa\U0001f1f8 (@CuriousRabitt) December 21, 2020
More from Werise
I like Stephen but I'll bite...
I saw a question asking what data and I answered him. I would gladly share the data & methodology. But I guess I am one of those lowly anons...
I saw a question asking what data and I answered him. I would gladly share the data & methodology. But I guess I am one of those lowly anons...
before accepting calculations from anonymous (or even non-anymous) sources, insist on a citation to original data so that it can be checked. I'm told (but haven't seen reference by Werise) that this comes from NYT json data https://t.co/6SD5ENF137. I'll comment on this data. pic.twitter.com/nqphPoqTa6
— Stephen McIntyre (@ClimateAudit) November 26, 2020
More from Politics
All the challenges to Leader Pelosi are coming from her right, in an apparent effort to make the party even more conservative and bent toward corporate interests.
Hard pass. So long as Leader Pelosi remains the most progressive candidate for Speaker, she can count on my support.
I agree that our party should, and must, evolve our leadership.
But changed leadership should reflect an actual, evolved mission; namely, an increased commitment to the middle + working class electorate that put us here.
Otherwise it’s a just new figure with the same problems.
I hope that we can move swiftly to conclude this discussion about party positions, so that we can spend more time discussing party priorities: voting rights, healthcare, wages, climate change, housing, cannabis legalization, good jobs, etc.
Hard pass. So long as Leader Pelosi remains the most progressive candidate for Speaker, she can count on my support.
The strange thing about the fight to displace Nancy Pelosi as Speaker of the House is that no one seems willing to run against her. https://t.co/VhBqf4KJom
— The New Yorker (@NewYorker) November 21, 2018
I agree that our party should, and must, evolve our leadership.
But changed leadership should reflect an actual, evolved mission; namely, an increased commitment to the middle + working class electorate that put us here.
Otherwise it’s a just new figure with the same problems.
I hope that we can move swiftly to conclude this discussion about party positions, so that we can spend more time discussing party priorities: voting rights, healthcare, wages, climate change, housing, cannabis legalization, good jobs, etc.
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.