Oh are we talking about Sheryl Sandberg again? Well, your reminder that disabled feminists, LGBQT feminists, and feminists of color criticised her ‘lean in’ deal from day one. Don’t let anyone retcon that out of existence.

Like, a pretty narrow slice of feminists actually endorse and support corporate feminism, they’re just white, nondisabled, straight, cis, and noisy so their voices have a bigger reach.
So if your impression is that ‘feminism’ gave her a ‘free pass’ maybe you should question your overall impression of feminism rather than continuing to centre a handful of people as ‘thought leaders’ or whatever.
Critics within feminism have been doing this work for a long time and have been getting shat on it for about as long and I'm tired of seeing them erased. But what do I know — I am, after all, not a feminist.
But I WILL say, from my not-a-feminist perspective, that people who aren’t feminists who are criticising feminism should maybe understand the movement more deeply beyond a handful of high profile celebrity feminists.
Also as a not-a-feminist, it really behooves not-a-feminists to acknowledge and centre the work being done within feminism to make it better, rather than engaging in formulaic dunking. Again, though, what do I know — I am, after all, not a feminist.
It’s my fervent hope that there will come a time when I feel welcome in feminism and I love working in solidarity with feminists who are trying to address these systemic issues. Part of that work involves following the movement and criticisms from both within and without closely.
Because it would be profoundly disrespectful to erase the work of people pushing for change.

More from Tech

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.

You May Also Like