
A few words on the passing of William Goldman: In addition to being a legendary screenwriter, he was a friend and mentor to so many other writers, offering guidance and support, directly influencing hundreds of films beyond his own work...



Butch Cassidy and the Sundance Kid

More from Writing
Things we don’t learn in this article: that the author wrote David Cameron’s speeches during the period when they were intentionally underfunding the NHS and other services, directly creating the problem the author is concerned about now.
We also don’t learn that the paper it’s written in stridently supported those measures and attacked junior doctors threatening strike action over NHS cuts and long working hours, accusing them of holding the country to ransom.
We aren’t reminded that NHS funding and the future of health provision was a central part of previous election campaigns, and that attempts to highlight these problems were swiftly stomped on or diverted and then ignored by most of the press, including the Times.
I’d underline here that “corruption” doesn’t just mean money in brown envelopes: it describes a situation where much of an organisation is personally motivated to ignore, downplay or divert from malfeasance for personal reasons - because highlighting them would be bad for careers
Foges was Cameron’s speechwriter at the height of austerity; Forsyth is married to the PM’s spokesman; Danny F is a Tory peer; Parris is a former MP; Gove used to write for them regularly, and that’s before we get to professional mates-with-ministers like Shipman or Montgomerie.
Today we learn health services are brutally underfunded with scant support for hard pressed staff, although it\u2019s left unclear who is responsible for that and it appears to be an exceptional, totally unpredicted phenomenon, like a freak weather event. pic.twitter.com/StwFR7RejE
— Flying_Rodent (@flying_rodent) January 25, 2021
We also don’t learn that the paper it’s written in stridently supported those measures and attacked junior doctors threatening strike action over NHS cuts and long working hours, accusing them of holding the country to ransom.
We aren’t reminded that NHS funding and the future of health provision was a central part of previous election campaigns, and that attempts to highlight these problems were swiftly stomped on or diverted and then ignored by most of the press, including the Times.
I’d underline here that “corruption” doesn’t just mean money in brown envelopes: it describes a situation where much of an organisation is personally motivated to ignore, downplay or divert from malfeasance for personal reasons - because highlighting them would be bad for careers
Foges was Cameron’s speechwriter at the height of austerity; Forsyth is married to the PM’s spokesman; Danny F is a Tory peer; Parris is a former MP; Gove used to write for them regularly, and that’s before we get to professional mates-with-ministers like Shipman or Montgomerie.
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.