Expecting equally sharp rally after some consolidation.
#WelspunIndia https://t.co/9b99KkCPu9

More from Aakash Gangwar

Time for a new thread on the possibilities I am looking for.
Do read it completely to understand the stance and the plan.


1. The moving average structure - Many traders just look at the 200 ma test or closing above/below it regardless of its slope. Let's look at all the interactions with 200 ma where price met it for the first time after the trend change but with 200 ma slope against it


One can clearly sense that currently it is one of those scenarios only. I understand that I might get trolled for this, but an unbiased mind suggests that odds are highly against the bulls for making fresh investments.

But markets are good at giving surprises. What should be our stance if price kept on rising? Let's understand that through charts. The concept is still the same. Divergent 200 ma and price move results in 200 ma test atleast once which gives good investment opportunities.


2. Zig-Zag bear market- There are two types of fall in a bear market, the first one is vertical fall which usually ends with ending diagonals (falling wedges) and the second one is zig zag one which usually ends with parabolic down moves.

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.