COFORGE
Double Top Buy, T20 Pattern - Bullish & Super Pattern - Bullish above 5281.96 daily close on 3% Box size chart. https://t.co/Iib4z27kHh
COFORGE
— Saket Reddy (@saketreddy) May 11, 2021
Double Top Buy above 3426.76 daily close on 1% box size chart. https://t.co/geOoLAc5XU pic.twitter.com/jxuoAVefqi
More from Saket Reddy
JUBLFOOD
Double Top Buy & T20 Pattern - Bullish above 4058.33 daily close on 1% Box Size chart. https://t.co/DPEehZwkS4
Double Top Buy & T20 Pattern - Bullish above 4058.33 daily close on 1% Box Size chart. https://t.co/DPEehZwkS4
JUBLFOOD
— Saket Reddy (@saketreddy) June 24, 2020
Achieved the second target of 1820 today, now near the first target of 1780!
Got a nice 15-20% move till now.
Trailing stop loss is the best thing one can do now! https://t.co/YidPZamyxz
JBCHEPHARM
Double Top Buy triggered above 1933.43 daily close on 3% Box size chart. https://t.co/eELxOeNmvg
Double Top Buy triggered above 1933.43 daily close on 3% Box size chart. https://t.co/eELxOeNmvg
JBCHEPHARM
— Saket Reddy (@saketreddy) July 16, 2021
Double Top Buy, Super Pattern - Bullish and T20 Pattern - Bullish triggered above 1886.26 daily close on 1% Box Size chart. https://t.co/bzIsbWjbEP pic.twitter.com/JQVkao635V
More from Coforge
COFORGE
Double Top Buy above 3426.76 daily close on 1% box size chart. https://t.co/geOoLAc5XU
Double Top Buy above 3426.76 daily close on 1% box size chart. https://t.co/geOoLAc5XU
COFORGE
— Saket Reddy (@saketreddy) May 6, 2021
Triple Top Buy above 3196.21 daily close on 1% Box size chart & Double Top Buy above 3195.68 daily close on 3% Box size chart. https://t.co/RI62IqiBoL pic.twitter.com/jvTNSR7W7P
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.