What to do?
Results of elections over the last five years signal to Progressives that we cannot simply continue thinking in traditional ways, proposing the usual, conventional solutions & hoping the pendulum could shift in their favour.
We need to wake the fuck
What to do?
We need to find, articulate, amplify & put into practice political answers to populism in a practical, solution-oriented & positive ways.
Nostalgia for the 1980s & 1990s
Surging sense of national identity
Desire for economic justice
Desire for greater security & stability
The 80s & 90s are associated with economic growth & job security. An idealised past that voters crave: they consider it the age of stable security, when their countries were still “independent & authentic”. They no longer feel at home in their own countries.
Populist voters feel that their roots, their history, their traditional values & often even their religion are threatened by a changing world.
uniformly designed shops, restaurants & cafés - although they welcome some benefits of globalisation, eg selection of food & goods, & cheap & simple travel.
They feel that the fruits of globalisation are distributed unequally in the world.
few decades: how far should the left stick by its core position & how far should it adapt to the changing environment?
So what strategies could we adopt?
European integration
Community
Patriotism
Socio-economic protection
Migration
Cooperation
a concept of the nation that point beyond an exclusive sense of nationalism. Some call it inclusive nationalism, others refer to it as liberal or positive nationalism, but many prefer to re-accent/redefine the word 'patriotism'.
social equality, tolerance & the willingness of the community’s members to mutually support one another: forging a national community in which everyone feels at home.
this issue from a left-wing perspective. However...
The rhetoric which says “migration has always existed & will always exist, there's nothing to be done about it”, or which asks citizens to just accept it, is doomed to fail.
In Britain we came very close in 2017, but fell short. Sadly, I think it optimistic that @UKLabour wins a majority in 2024.
More from Politics
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.