First, I don't believe that "cancel culture" exists. There is no systemic problem of people being fired because their ideas are too radical. People generally get fired because they say something bigoted or do something that's fire-able anyway. This is a separate problem:

There is a problem of institutions that treating Internet commenters as if the customer is always right, and everyone is a customer. I think it partly has to do with viewing news as more of a consumer product than something that has a public service element.
And employers need to know how to differentiate between bad faith critiques and legitimate concerns, & use (godforbid) critical thinking skills to separate the two. They need to consider the complaints on their own merits, & in the context of the employee's work and known intent
Just to use an example; someone my TL compared Will Wilkinson's firing to James Damore's, as if either of those cases were about radical ideas. I find what Damore was advancing despicable, but from a corporate perspective, he was also a walking gender discrimination lawsuit.
There were multiple reasons to fire Damore, and at least one that was rooted in sheer practicality. Wilkinson and Wolfe's firings were both predicated upon taking the critiques of bad faith Internet commenters at face value, as if they were meaningful and sincere.
As if the customer is always right. And in Wolfe's case, you also had to read into her comment. For some people seeing Biden's plane land might produce and emotional effect because it's a historic moment, not because you're partisanly swooning over Biden.
But even if she had been expressing relief that Trump was out of office (which many Republicans are happy about too), it's not very different from things her more powerful colleagues have said on Twitter. She got fired because she's lower in the hierarchy.
If the Times is going to have a policy that none of its reporters can express a personal opinion about current events or display any emotion, it needs to be equally applied. And have the politics desk would have been fired by now if it had been.
I also think that kind of policy would be stupid, and impossible to enforce. Contrary to the bad faith critiques, these things do not remove or cover up bias. Opinions are something everyone has and they're a product of critical thinking.
American journalism has really undermined itself by using language that implies that journalistic objectivity is the same as neutrality, and non-thinking reporting of empirical facts in some kind of arbitrary format.
Every reporter has opinions because every human does. Every reporter has some kind of partisan leanings because they have opinions about the parties too. Journalistic objectivity should really be called journalistic remove, which is more accurate.
No human is capable of objectivity, in the way that bad faith critics allege is the goal, because no one is omniscient. "Journalistic objectivity" is about not letting opinions get in the way of seeing what the truth is and reporting it.
And a lot of people don't understand this because media literacy is terrible, but also because "objectivity" is entirely the wrong word and news execs keep stupidly using it. And just to come back to a point: Wolfe's firing was about her lack of power at the Times, not her bias.

More from Culture

I just finished Eric Adler's The Battle of the Classics, and wanted to say something about Joel Christiansen's review linked below. I am not sure what motivates the review (I speculate a bit below), but it gives a very misleading impression of the book. 1/x


The meat of the criticism is that the history Adler gives is insufficiently critical. Adler describes a few figures who had a great influence on how the modern US university was formed. It's certainly critical: it focuses on the social Darwinism of these figures. 2/x

Other insinuations and suggestions in the review seem wildly off the mark, distorted, or inappropriate-- for example, that the book is clickbaity (it is scholarly) or conservative (hardly) or connected to the events at the Capitol (give me a break). 3/x

The core question: in what sense is classics inherently racist? Classics is old. On Adler's account, it begins in ancient Rome and is revived in the Renaissance. Slavery (Christiansen's primary concern) is also very old. Let's say classics is an education for slaveowners. 4/x

It's worth remembering that literacy itself is elite throughout most of this history. Literacy is, then, also the education of slaveowners. We can honor oral and musical traditions without denying that literacy is, generally, good. 5/x
. THREAD 1/x

David Baddiel is getting lots of coverage and feedback on his book which again focuses on so called 'left wing' antisemitism.

I will start by saying that I have seen antisemitic comments made by Labour members and some genuine cases.

However, I have huge concerns.


2/x

Let's look in detail at this article written in April 2019 in the @Guardian - and I will explain the concerns.

The areas highlighted guide you to believe this was all Labour - IT WASN'T.

It also occurred before 2015! Detail follows...

https://t.co/cK59FP83aG


3/x

So as you see the writer of this rather deceitful piece starts with

"THAT CHANGED IN SEPTEMBER 2015" 🙄

This was done to point the timeframe as Corbyn's leadership. Yet the article goes on to describe things that are not even related to Labour, which occurred in 2014.


4/x

So... What in fact the @Guardian writer is discussing here is this case - where a group of Neo-Nazi's spent months inflicting abuse on Jewish MP Luciana Berger

All the detail is in the Court Notes when Bonehill-Paine was sentenced by the judge.

https://t.co/wAyo6Yro5Q


5/x

The Justice sentencing remarks to Neo-Nazi explain the previous cases too. See the date 2014.

Yet the Guardian writer refers to this NON LABOUR case to effectively make her article a lie.

"Star of David" - this was Garron Helm another neo-Nazi..

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.