1/ Further thoughts on @DavidAFrench's important essay on #ChristianNationalism.

It's great to see a leading evangelical thinker publicly engaging the topic.

But....

2/ It would be even better if @DavidAFrench would engage with work on #ChristianNationalism by scholars and journalists like:

@ndrewwhitehead @socofthesacred @praxishabitus @sarahposner @kathsstewart @AntheaButler @Nicholef and yours truly @GorskiPhilip

Also...
3/ With the work of black theologians such as:

Willie Jennings, @JemarTisby @stewartdantec @esaumccaulley to name just a few.

If he did, then....
4/ He'd know that there are much better and more nuanced definitions of #ChristianNationalism than the one offered by @ThomasSKidd, who is a smart guy, but not a scholar of the subject.

Plus...
5/ He'd know that the phenomenon is, in fact, much more widespread than he implies, not just amongst white evangelicals but also amongst non-evangelical white Protestants and white Catholics....See "Taking America Back for God" for the receipts.

So, why do I keep saying "white"?
6/ Because, as all this work shows, #ChristianNationalism in the US must be understood as *White* #ChristianNationalism. White Supremacism has left a deep and enduring impression on American Christianity that exerts effects even in the absence of racial prejudice.

How so?
7/ An example: Christian libertarianism.

As many scholars have shown, including @praxishabitus and I, conservative evangelicals were NOT economic conservatives 100 years ago. They were economic progressives!

What happened?
8/ Basically, the New Deal and the Civil Rights Movement.

How could you push back against social and economic policies that might've helped Black folks? And without screaming the "n-word"? Replace it with the "m-word": MARKETS!

This was a completely conscious strategy, too.
9/ To be clear: I am NOT suggesting that @DavidAFrench is some kind of racist. I know the very opposite to be the case. Unlike many of his co-religionists, he recognizes that systemic racism is not some fiction cooked up in the seminar room. It's real.

More from Society

Brief thread to debunk the repeated claims we hear about transmission not happening 'within school walls', infection in school children being 'a reflection of infection from the community', and 'primary school children less likely to get infected and contribute to transmission'.

I've heard a lot of scientists claim these three - including most recently the chief advisor to the CDC, where the claim that most transmission doesn't happen within the walls of schools. There is strong evidence to rebut this claim. Let's look at


Let's look at the trends of infection in different age groups in England first- as reported by the ONS. Being a random survey of infection in the community, this doesn't suffer from the biases of symptom-based testing, particularly important in children who are often asymptomatic

A few things to note:
1. The infection rates among primary & secondary school children closely follow school openings, closures & levels of attendance. E.g. We see a dip in infections following Oct half-term, followed by a rise after school reopening.


We see steep drops in both primary & secondary school groups after end of term (18th December), but these drops plateau out in primary school children, where attendance has been >20% after re-opening in January (by contrast with 2ndary schools where this is ~5%).

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.