What I Read In 2020 (A Thread) [ Let me know if you read any of these because I want someone to talk to about these books or if you want my full thoughts on anything ]









More from Culture
. 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..
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.
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.