THREAD
Can we talk a little bit about what Cal McNair is about to do to the NFL, and the leverage owners have had over players for roughly 100 years?
I would be FASCINATED to know what the NFL league office and other owners are thinking about the Watson/Texans standoff
The culture is so bizarre that people are discussing the following questions behind the scenes:
Would they draft Zach Wilson, a good prospect but one who is Mormon?
I don't know who this Cary McNair guy is, but his bio seems way better than Cal's - https://t.co/SkowcJRQSR
More from Sport
Thiago Alcantara, a THREAD
https://t.co/JxxXhI1jJd
https://t.co/MS5UpCuN7m
https://t.co/E4CUMbF2aN
https://t.co/b7dYAyANSh
https://t.co/JxxXhI1jJd
Thiago "home can play" Alcantara
— Orsteen \U0001f489 (@_orsteen) January 22, 2021
https://t.co/MS5UpCuN7m
Thiago \u201cthe ball Na your pikin, send am message\u201d Alcantara pic.twitter.com/IG4IwH07cK
— Man of Letters. (@Letter_to_Jack) January 22, 2021
https://t.co/E4CUMbF2aN
Thiago 'Just dey go i don see you already' Alcantara
— Aremu Pokipoki (@prinzgbemi) January 22, 2021
https://t.co/b7dYAyANSh
Thiago "Play with your nearest man" Alcantara
— \xc0GB\xc0! (@Oli_Ekun) January 22, 2021
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.