Apollo Hospitals and a clear breakdown. Although the signal came much earlier with a false breakout. Now is the second best exit.
More from The_Chartist 📈
H&S tops with ascending/descending necklines https://t.co/cmRRHp5rlh
Sir Edwards & Magee discussed sloping necklines in H&S in their classical work. I am considering this breakdown by Affle as an H&S top breakdown with a target open of 770.
— The_Chartist \U0001f4c8 (@charts_zone) May 25, 2022
The target also coincides with support at the exact same level. pic.twitter.com/n84kSgkg4q
More from Apollohospitals
Almost 3 months taken.
Apollo Hospitals 2915 to 3450, near target.
SL of just 2.5% was not breached for 3 months, imagine the strength in this counter since then.
Net returns nearly 20% in 3 months.
Apollo Hospitals 2915 to 3450, near target.
SL of just 2.5% was not breached for 3 months, imagine the strength in this counter since then.
Net returns nearly 20% in 3 months.
Apollo Hospitals
— Prem Doshi \U0001f1ee\U0001f1f3 (@StocksResearch) April 5, 2021
CMP 2915
SL of 2840
Target 3500+
Covid wave 2 causing a sharp rally in diagnostic lab stocks, should spill over to hospital stocks too, apollo the only F&O stock in hospital sector. pic.twitter.com/F6tS8TX1s2
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.