๐Ÿ‘€ ๐Ÿ‘‡๐Ÿผ saving all these post from Lin Wood in this thread.

More from Government

The Government is making the same mistakes as it did in the first wave. Except with knowledge.

A thread.


The Government's strategy at the beginning of the pandemic was to 'cocoon' the vulnerable (e.g. those in care homes). This was a 'herd immunity' strategy. This interview is from


This strategy failed. It is impossible to 'cocoon' the vulnerable, as Covid is passed from younger people to older, more vulnerable people.

We can see this playing out through heatmaps. e.g. these heatmaps from the second


The Government then decided to change its strategy to 'preventing a second wave that overwhelms the NHS'. This was announced on 8 June in Parliament.

This is not the same as 'preventing a second wave'.

https://t.co/DPWiJbCKRm


The Academy of Medical Scientists published a report on 14 July 'Preparing for a Challenging Winter' commissioned by the Chief Scientific Adviser that set out what needed to be done in order to prevent a catastrophe over the winter

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.