#Radico reached our 1st target and is trading at 870 now.
@MD_ABNSTOCKS
#Radico #StockToWatch #Stock #Equity #StockMarket
— Team MD&ABN (@team_md_abn) July 10, 2021
CMP - 779
Entry - once price closes above 783 in the hourly chart
Pattern invalid below - 736.50
Possible upside Levels
Conservative - 866
Aggressive - 944@caniravkaria pic.twitter.com/6xD7oywkNC
More from Team MD&ABN
#DeepakNtr From 1875 to 2076 till now.. Marching well towards 2355.
@MD_ABNSTOCKS
@MD_ABNSTOCKS
#DeepakNtr #StockToWatch
— Team MD&ABN (@team_md_abn) July 5, 2021
Entry - any dip towards 1875 is a buy
A counter will become weak if it closes below 1710 in a daily time frame.
A possible upside level is 2355 pic.twitter.com/IPlHPvBXFI
#TataSteel 1st target is done, 1481 is the high posted till now. Marching well towards 1600 now.
#TataSteel #NiftyMetal #StockToWatch
— Team MD&ABN (@team_md_abn) July 7, 2021
CMP - 1224.80
Buy range - 1190-1200
Upside Possible Levels
Conservative - 1395
Aggressive - 1600
The view will be invalid if closes below 1129 pic.twitter.com/e6MabwG9YI
More from Radico
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.