I finished reading Men Trapped in Men’s Bodies. It was quite gruelling to read.
Here are some things women should know:
There is NO aspect of being female or perceived as feminine that is too mundane or too terrible for an autogynephilic transsexual to find sexually arousing.
More from Society
I've seen many news articles cite that "the UK variant could be the dominant strain by March". This is emphasized by @CDCDirector.
While this will likely to be the case, this should not be an automatic cause for concern. Cases could still remain contained.
Here's how: 🧵
One of @CDCgov's own models has tracked the true decline in cases quite accurately thus far.
Their projection shows that the B.1.1.7 variant will become the dominant variant in March. But interestingly... there's no fourth wave. Cases simply level out:
https://t.co/tDce0MwO61
Just because a variant becomes the dominant strain does not automatically mean we will see a repeat of Fall 2020.
Let's look at UK and South Africa, where cases have been falling for the past month, in unison with the US (albeit with tougher restrictions):
Furthermore, the claim that the "variant is doubling every 10 days" is false. It's the *proportion of the variant* that is doubling every 10 days.
If overall prevalence drops during the studied time period, the true doubling time of the variant is actually much longer 10 days.
Simple example:
Day 0: 10 variant / 100 cases -> 10% variant
Day 10: 15 variant / 75 cases -> 20% variant
Day 20: 20 variant / 50 cases -> 40% variant
1) Proportion of variant doubles every 10 days
2) Doubling time of variant is actually 20 days
3) Total cases still drop by 50%
While this will likely to be the case, this should not be an automatic cause for concern. Cases could still remain contained.
Here's how: 🧵
One of @CDCgov's own models has tracked the true decline in cases quite accurately thus far.
Their projection shows that the B.1.1.7 variant will become the dominant variant in March. But interestingly... there's no fourth wave. Cases simply level out:
https://t.co/tDce0MwO61
Just because a variant becomes the dominant strain does not automatically mean we will see a repeat of Fall 2020.
Let's look at UK and South Africa, where cases have been falling for the past month, in unison with the US (albeit with tougher restrictions):
Furthermore, the claim that the "variant is doubling every 10 days" is false. It's the *proportion of the variant* that is doubling every 10 days.
If overall prevalence drops during the studied time period, the true doubling time of the variant is actually much longer 10 days.
Simple example:
Day 0: 10 variant / 100 cases -> 10% variant
Day 10: 15 variant / 75 cases -> 20% variant
Day 20: 20 variant / 50 cases -> 40% variant
1) Proportion of variant doubles every 10 days
2) Doubling time of variant is actually 20 days
3) Total cases still drop by 50%
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.