#MAITHANALLOYS Further update 👇
Rounding Bottom pattern 🧐 https://t.co/EONRI5MOSZ
#Maithanalloys
— Pranay Prasun (@PranayPrasun) May 3, 2021
Highlighted this gem on 21st March at 560 level for big target.\U0001f918
Added to my portfolio after breakout (660 level)
Go through below thread for more details \U0001f447 https://t.co/IPRYa7pLlV
More from Pranay Prasun
Another one #Lupin🎯
**Don't miss this move**
All alerts in advance🔥👇
Expecting breakout retest in weekly chart near 1130 level
**Don't miss this move**
All alerts in advance🔥👇
#LUPIN #cnxpharma Consolidation Consolidation & Consolidation
— Pranay Prasun (@PranayPrasun) April 18, 2021
but in tight range \U0001f9d0\U0001f447@Jitendra_stock @gogrithekhabri @piyushchaudhry @caniravkaria https://t.co/8G4KQjYM4i pic.twitter.com/yDIX71tnOp
Expecting breakout retest in weekly chart near 1130 level
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.