1 January 2021 #MAGAanalysis #HappyNewYear2021

The Forward View + A Table of Contents For Our J.E. Dyer @OptimisticCon's 10 Threads

To be sure, happiness in this New Year's moment has an even more ephemeral feeling than usual, and perhaps by a good deal. Yet it is here.

More from Pasquale "Pat" Scopelliti

More from Society

@danielashby @AdamWJT @Greens4HS2 @TheGreenParty @GarethDennis @XRebellionUK @Hs2RebelRebel @HS2ltd I'll bite. Let's try to keep it factual. There's a reasonable basis to some aspects of this question, that it might be possible to agree on. Then there are other, more variable, elements which depend on external factors such as transport and energy policy. /1

@AdamWJT @Greens4HS2 @TheGreenParty @GarethDennis @XRebellionUK @Hs2RebelRebel @HS2ltd First up, we know reasonably well how much energy it takes to propel a high-speed train along the HS2 route. We can translate that into effective CO2 generated by making some assumptions about how green the electricity grid is. /2

@AdamWJT @Greens4HS2 @TheGreenParty @GarethDennis @XRebellionUK @Hs2RebelRebel @HS2ltd Secondly, we have a reasonable grasp of how much CO2 is going to be generated by building HS2 - there are standard methods of working this out, based on the amount of steel, concrete, earthmoving, machine-fuelling etc required. /3

@AdamWJT @Greens4HS2 @TheGreenParty @GarethDennis @XRebellionUK @Hs2RebelRebel @HS2ltd Thirdly, we can estimate how much CO2 is generated by cutting down trees, and how much is captured by planting new trees. We can also estimate how much CO2 is needed to keep the railway running and generated by maintaining the track /4

@AdamWJT @Greens4HS2 @TheGreenParty @GarethDennis @XRebellionUK @Hs2RebelRebel @HS2ltd We know how much CO2 is saved by moving goods by freight train on the lines freed up by moving the express trains on to HS2, rather than by truck. /5

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.