More from Cnxitlongterm
What happened to IEX can happen to CNXIT. Savdhaan rahe, satark rahe. Reiterating it again, every falling wedge/channel, RSI divergence is not a reversal signal.
#CNXIT
#CNXIT
Watching the marked zone to be tested. If it doesn't cross it, then most probably a parabolic downmove towards 24k. That would lead to even large caps cracking just like Small and Midcaps. #CNXIT https://t.co/FxbzP5vlBr pic.twitter.com/FSqcSqTQM9
— Aakash Gangwar (@akashgngwr823) June 21, 2022
Parabolic move has been triggered. Let's have 27k. That could be the buying zone for IT names.
#CNXIT https://t.co/bJeKTMoCji
#CNXIT https://t.co/bJeKTMoCji
The current formation might look like a falling wedge, but the way moving averages are placed, it looks like a falling wedge which can lead to a parabolic downmove for the marked target. #CNXIT pic.twitter.com/GmXOI3HmUN
— Aakash Gangwar (@akashgngwr823) May 10, 2022
We often hear that prediction in markets is a nasty game, but we don't really have to believe everything we read on social media. Do we? As long as you maintain good accuracy in your predictions, you will do absolutely great.
#CNXIT https://t.co/w3qedea7T6
#CNXIT https://t.co/w3qedea7T6
Almost there. Quick move. It can spend time over here before the next leg of fall. Let's see.#NIFTYIT https://t.co/GOB28HRvMp pic.twitter.com/6sNc7j8gEU
— Aakash Gangwar (@akashgngwr823) March 9, 2022
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.