#NiftyMetals this correction is healthy. Gap of 7th May filled. May test 5019 levels. Bullish above 5400 levels again.
More from Dare2Dream
#BHEL 57 to 73 in 4 trading days🛩️🛩️.
Around 73 / 74 - is the first target - next targets around 110.
Remember :Keeping a stop is always important if one is trading.
@caniravkaria https://t.co/ViHbzJTfQ6
Around 73 / 74 - is the first target - next targets around 110.
Remember :Keeping a stop is always important if one is trading.
@caniravkaria https://t.co/ViHbzJTfQ6
#BHEL looks good for targets of 74+ https://t.co/jrRyXc5FLL pic.twitter.com/KWkzeHSs0D
— Dare2Dream (@Dare2Dr10109801) May 6, 2021
#Graphite Could now be heading to 880 / 900 levels. https://t.co/qO6QzoYrBt
#Metals All in one place#Sail \U0001f680 #TataSteel\U0001f680 #Vedl\U0001f6eb #Jswsteel\U0001f680\U0001f680 #Graphite\U0001f680 #Heg\U0001f680
— Dare2Dream (@Dare2Dr10109801) April 29, 2021
Very shortly I expect #Hindcopper as well, still at the launch pad. #Vedl #Hindalco yet to pick up pace.@caniravkaria https://t.co/eeOxZ7WWvo
More from Metals
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.