As long as 15775 is not breached, bull case remains. Will be portfolio cautious only below 16000. Otherwise the path on chart is the way 5th wave should play out till Sept-Oct 2022.

16350 waapis nahi dikhega in 2022, woh aap bhi dekh saktey hai - IF 5TH PLAYS OUT. 😃

#Nifty

More from Harsh / 허쉬

Invalidation level can be brought up to 4900 also.. #BajajFinance
#Bharti : Keeping above 640 now, impulse counts should play out for 2840 minimum. (Remember its a monthly chart)

Below 640, counts need to be revalidated. https://t.co/1e7hs0ZkxR

More from Niftylongterm

#Nifty watch this trendline to be taken out for a good long trade! https://t.co/nC32qh2rOO

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.