I’m not a scientist, so obviously do correct me if I’m wrong. (Heck, this is twitter, I don’t need to ask that do I?)
BUT a virus doesn’t mutate in *nothing*, does it, it doesn’t mutate when it’s on the handle of the supermarket door or even in the air you’ve just breathed out.
But what did we do?
And you’ll never guess what’s happened now!
IT FUCKING ADAPTED.
And if a fool like me, whose weakest science was biology, who didn’t take it any further than GCSE, could see this, why couldn’t they?
More from Twitter
Today's Twitter threads (a Twitter thread).
Inside: Privacy Without Monopoly; Broad Band; $50T moved from America's 90% to the 1%; and more!
Archived at: https://t.co/QgK8ZMRKp7
#Pluralistic
1/
This weekend, I'm participating in Boskone 58, Boston's annual sf convention.
https://t.co/2LfFssVcZQ
Tonight, on a panel called "Tech Innovation? Does Silicon Valley Have A Mind-Control Ray, Or a Monopoly?" at 530PM Pacific.
2/
Privacy Without Monopoly: A new EFF white paper, co-authored with Bennett Cyphers.
https://t.co/TVzDXt6bz6
3/
Broad Band: Claire L Evans's magesterial history of women in computing.
https://t.co/Lwrej6zVYd
4/
$50T moved from America's 90% to the 1%: The hereditary meritocracy is in crisis.
https://t.co/TquaxOmPi8
5/
Inside: Privacy Without Monopoly; Broad Band; $50T moved from America's 90% to the 1%; and more!
Archived at: https://t.co/QgK8ZMRKp7
#Pluralistic
1/
This weekend, I'm participating in Boskone 58, Boston's annual sf convention.
https://t.co/2LfFssVcZQ
Tonight, on a panel called "Tech Innovation? Does Silicon Valley Have A Mind-Control Ray, Or a Monopoly?" at 530PM Pacific.
2/
Privacy Without Monopoly: A new EFF white paper, co-authored with Bennett Cyphers.
https://t.co/TVzDXt6bz6
3/
Today, @EFF published "Privacy Without Monopoly: Data Protection and Interoperability," a major new paper by Bennett Cyphers and me. https://t.co/Ma2FE2vZ9u
— Cory Doctorow #BLM (@doctorow) February 13, 2021
1/ pic.twitter.com/RzCkQdQRxy
Broad Band: Claire L Evans's magesterial history of women in computing.
https://t.co/Lwrej6zVYd
4/
One of the most Monkey's Paw things about my life is my relationship to books. When I was a teenager, I read all the way through the school and public libraries, spent everything I had on books, and still couldn't get enough and dreamt of more.
— Cory Doctorow #BLM (@doctorow) February 13, 2021
1/ pic.twitter.com/Lgkdk5a7YA
$50T moved from America's 90% to the 1%: The hereditary meritocracy is in crisis.
https://t.co/TquaxOmPi8
5/
Inequality requires narrative stabilizers. When you have too little and someone else has more than they can possibly use, simple logic dictates that you should take what they have.
— Cory Doctorow #BLM (@doctorow) February 13, 2021
1/ pic.twitter.com/BUFyq9H2n4
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.