#Nifty

So now that Nifty has undergone ABC correction in the expected manner, what to expect next?

I think we have started larger degree wave 3, once 16800 was crossed.

16800 is the reference level now. We will get more sense by end of next week/ month. https://t.co/KsziuUpZxU

#NIFTY

If 17445 is taken out, then may be we are heading to fresh new all time on Nifty.

Things may pan out way faster than expected.
#NIFTY

Zoomed in cross-section of the chart above.

Wave 3 of 1 should have started today, which can take Nifty to fresh all time highs.
#NIFTY

So now Nifty is moving more clearly on the expected path, what's next?

Nifty has started longer term wave 3 advancement, pending final confirmation of HH by crossing 17800.

In Wave 1 of 3, can expect a move to 20k+.
In terms of longer term wave structure:

Wave 1: 7500 to 18600
Wave 3: 15700 to 35000+

And this can pan out over next 2 years or so.

Since wave 2 was a shallow correction, wave 4 can potentially be a deeper correction.

More from Mayank Narula

More from Nifty

#Nifty -- Going good so far forming triangle as expected.

Till it breakouts expect pendulum swings within this structure.

I am positive for 19300-20000 above 18350.

Bottoms 16800-17000 in place and 200dema at 16600. Dont see any big cut. @moneyworks4u_fa https://t.co/lceGFlDyRM

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.