#TATAELXSI
Hottest stock of social media 😷😷
Better on Retest
Looking 11500++
More from jitu
More from Tataelxsi
Tata Elxsi - One more base formation. If you pick books written by legends, all says once a stock makes 4-6 bases, the maximum juice is out of it. However, with my chart reading, I am observing Indian market is too different. must follow the price. https://t.co/1nqNu4kouk
Sir tata elxsi??
— NITISH KUMAR OJHA (@nkoiiiiiii) October 1, 2021
Tata Elxsi - all-time high again. A lot to learn from this chart. ✅ https://t.co/IooKK2EYpy
Tata Elxsi (W) - near to the resistance zone again 5th time. @nishkumar1977 @suru27 @rohanshah619 @indian_stockss @sanstocktrader @BissaGauravB @RajarshitaS @PAVLeader @Rishikesh_ADX @VijayThk @Investor_Mohit @TrendTrader85 @jitendra_stock pic.twitter.com/aIC5kO8XqA
— Steve Nison (@nison_steve) December 18, 2020
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.