IEX
Double Top Buy & T20 Pattern - Bullish triggered above 571.53 daily close on 1% Box Size chart. https://t.co/BQxUdNo5fG

IEX
— Saket Reddy (@saketreddy) May 4, 2021
The trio meet once again on the chart!
Double Top Buy, T20 Pattern - Bullish & Super Pattern - Bullish above 380.44 daily close on 3% Box size chart. https://t.co/IPPpzuX2st pic.twitter.com/zpFxDiEx5j
More from Saket Reddy
HDFC
Double Top Buy above 2864.83 daily close on 1% Box Size chart. https://t.co/oP7KnYn7R8
Double Top Buy above 2864.83 daily close on 1% Box Size chart. https://t.co/oP7KnYn7R8

HDFC
— Saket Reddy (@saketreddy) February 2, 2021
High Quality standalone business, Holds double digit stakes in High quality group companies like HDFCBANK & HDFCLIFE.
Double Top buy & ABC Pattern breakout above 2698.8 daily close on 1% box size chart & Double top buy above 2756.62 on 3% box size chart. https://t.co/6ozyrPMgIG pic.twitter.com/fXRcAI9Kws
More from Iex
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.