Today, barely 700,000 of the 3.8 million people live in those four cities.
1) Since 1970, the United States has increased its population by 64%.
Northeast Ohio, a 12-county region with more people than Connecticut, has lost 7% of its population over this same time period, shrinking from 4.1 million to 3.8 million people.
Today, barely 700,000 of the 3.8 million people live in those four cities.
Today, median household income in metro D.C. is 82% higher than in metro Cleveland.
If you look at this great analysis by @InnovateEconomy you will see that Ohio is one of the worst-performing states in terms of expanding poverty.
https://t.co/ZGoK2qqN1W
In 2008, Barack Obama won the 12-county Northeast Ohio region by nearly 400,000 votes.
In 2020, Joe Biden won this heavily-Democratic region by only 92,000 votes.
And I live here in urban Ohio. I've lived here for almost 5 decades. I can see what all of this looks like here on the ground.
It doesn't look pretty.
More from Economy
Latest @SouledOutWorld articles:
(Article Thread)
All in one convenient location to access.
https://t.co/TuyltZTyW0
https://t.co/XJJRvpLRQE
https://t.co/NeeFCfMkP2
https://t.co/yFtbIgqzzm
(Article Thread)
All in one convenient location to access.

https://t.co/TuyltZTyW0
True State of the Nation
— Secret SoSHHiety (@SouledOutWorld) December 19, 2020
You think you know what's coming... but you don't...https://t.co/MVoIuxgaWX pic.twitter.com/DtF2Q53HrT
https://t.co/XJJRvpLRQE
Truth About Antarctica
— Secret SoSHHiety (@SouledOutWorld) December 19, 2020
Why? Scalar EM Antennas are kept at Antarctica; Scalar EM weaponry is the anonymous weapon to be used by the White Horse of Rev 6.https://t.co/7CDzmQfLSX pic.twitter.com/0400oCN8io
https://t.co/NeeFCfMkP2
The Finger (fuck you/fuck the world)
— Secret SoSHHiety (@SouledOutWorld) December 18, 2020
The middle finger is the Saturn finger.https://t.co/BsrsBE3f5h pic.twitter.com/ZJqZll8lU1
https://t.co/yFtbIgqzzm
Bread and Circuses
— Secret SoSHHiety (@SouledOutWorld) December 18, 2020
Bring in the clowns & the fast food...https://t.co/SZAlfkqTI3 pic.twitter.com/gLys0mNMIq
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.