6 trends in #TATAELXSI last 24 odd years...you only needed 1. https://t.co/iOkww27EgO
congratulations to #MiAllcap holders. If you have been invested since Oct 20 or earlier, you have a 6 bagger in your portfolio! https://t.co/sAKICo38eC
— Alok Jain \u26a1 (@WeekendInvestng) March 28, 2022
More from Alok Jain ⚡
More from Tataelxsilongterm
Reasons-
1. Long term channel top.
2. Curvature shift of 20 and 50 WMA along with price hitting 20 WMA frequently.
3. Overall weakness in IT sector.
4. For reference, study reliance top in August 2020, study Nasdaq Weekly chart and the top made in Nov 2021.
#tataelxi https://t.co/RmJa5LrdAP
1. Long term channel top.
2. Curvature shift of 20 and 50 WMA along with price hitting 20 WMA frequently.
3. Overall weakness in IT sector.
4. For reference, study reliance top in August 2020, study Nasdaq Weekly chart and the top made in Nov 2021.
#tataelxi https://t.co/RmJa5LrdAP
I have traded the current fav Tata Elxi from 2200 to 4500. No regret on missing out rest of the move because I am not an investor. Now there are many technical red flags. I might be trolled but 10.5k looks max target while 5k or 3-4 years of sideways looks inevitable.#tataelxi
— Aakash Gangwar (@akashgngwr823) March 26, 2022
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.