More from All
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.
On the occasion of youtube 20k and Twitter 70k members
A small tribute/gift to members
Screeners
technical screeners - intraday and positional both
before proceeding - i have helped you , can i ask you so that it can help someone else too
thank you
positional one
run - find #stock - draw chart - find levels
1- Stocks closing daily 2% up from 5 days
https://t.co/gTZrYY3Nht
2- Weekly breakout
https://t.co/1f4ahEolYB
3- Breakouts in short term
https://t.co/BI4h0CdgO2
4- Bullish from last 5
intraday screeners
5- 15 minute Stock Breakouts
https://t.co/9eAo82iuNv
6- Intraday Buying seen in the past 15 minutes
https://t.co/XqAJKhLB5G
7- Stocks trading near day's high on 5 min chart with volume BO intraday
https://t.co/flHmm6QXmo
Thank you
A small tribute/gift to members
Screeners
technical screeners - intraday and positional both
before proceeding - i have helped you , can i ask you so that it can help someone else too
thank you
positional one
run - find #stock - draw chart - find levels
1- Stocks closing daily 2% up from 5 days
https://t.co/gTZrYY3Nht
2- Weekly breakout
https://t.co/1f4ahEolYB
3- Breakouts in short term
https://t.co/BI4h0CdgO2
4- Bullish from last 5
intraday screeners
5- 15 minute Stock Breakouts
https://t.co/9eAo82iuNv
6- Intraday Buying seen in the past 15 minutes
https://t.co/XqAJKhLB5G
7- Stocks trading near day's high on 5 min chart with volume BO intraday
https://t.co/flHmm6QXmo
Thank you