More from Nishant Kumar
More from Maithanalloys
Price playing within the resistance zone. Let it be. This is a healthy sign and it would be good if the stock continues to consolidate in this zone for a few days/weeks. This would help RSI cool down, and also lead to change of hands!
#MaithanAlloys 1022
#MaithanAlloys 1022
#MaithanAlloys 940
— Nishant Kumar (@nishkumar1977) June 18, 2021
970 - 1030 is going to offer stiff resistance.
We are approaching 4 digit mark and ATH territory!! Fingers crossed!!https://t.co/bMgkKffyXc https://t.co/8DSt1yHPN8
Maithan Alloys - Trend change above 700 done
Retest of support at 700-710 is a great opportunity cmp 761+
Potential target 1000-1300-1500 in next 1-1.5 year
It has Pole & Flag pattern on multiyear log scale which gives a taget of 2000+ and more over next 3-4 years https://t.co/aCDDcGVqOc
Retest of support at 700-710 is a great opportunity cmp 761+
Potential target 1000-1300-1500 in next 1-1.5 year
It has Pole & Flag pattern on multiyear log scale which gives a taget of 2000+ and more over next 3-4 years https://t.co/aCDDcGVqOc
Yes please @shivaji_1983 sir. Share your chart view on MAITHAN ALLOYS
— Anushka (@AnushkaDas28) June 1, 2021
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.