Copper breaching the rising Trendline.
Weekly Candles, so we still need to wait.
Earlier two tweets on Copper:
1. Copper - EM:
https://t.co/WogWRMIMHH
and,
2. Copper - Gold
https://t.co/Cq2zcn4bi3

Amazingly super positive correlation between Emerging Markets and Copper.
— Piyush Chaudhry (@piyushchaudhry) June 2, 2021
*MSCI Emerging Markets ETF #EEM
*Copper Futures #Comex pic.twitter.com/rVAwfqvqD4
More from Piyush Chaudhry
#NIFTY
15 Months to this post. No change in the larger projections.
15 Months to this post. No change in the larger projections.
Long Term Chart of the Year.#NIFTY - Wave 5 (Cycle Degree) Target Zone of 25000-34000 by 2024-2027.
— Piyush Chaudhry (@piyushchaudhry) December 19, 2020
Reassessment on a breach below Blue Trendline. A breach is not a necessary invalidation. Depends on internals.
The dashed path is for representative purpose only. #ElliottWave pic.twitter.com/1xVY4OSr5T
More from Copper
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.