#iex look how it reached the yellow line #hporb
closing above 428 would be swell https://t.co/uZj5paFe6Q

from the analysis done few sessions ago for #iex Indian energy Exchange till now #hporb https://t.co/LnqCcCjxqq pic.twitter.com/tMcubrT6JP
— RB\U0001f4ab The Trend Trader (@usb_3Dot0) August 15, 2021
More from Iex
#IEX
see how demand supply zone or Turning points working simple entry close abv zone exit close below zone Ride to next levels
#AhmedabadNest #process https://t.co/MEJ2WvLHoF
see how demand supply zone or Turning points working simple entry close abv zone exit close below zone Ride to next levels
#AhmedabadNest #process https://t.co/MEJ2WvLHoF

#ValueInvesting #GrowthInvesting #momentum #Mindset #IEX https://t.co/35n8Y60GhX
— NISHSHKUMAR JAANI (@NishshkumarJaan) July 9, 2021
Running bullish ABC n close abv 404 Anchor Ft buy sl 350 on closing basis tgt 495-575#Relativestrength #outperformance #AhmedabadNest #investing #India #NISHSHKUMAR pic.twitter.com/CNr1c9PXqy
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.