CDSL :
Breaking out on Medium-term !!!
#cdsl
#Nifty
#Banknifty
#EquityDynamo
More from Equity Dynamo
Alkylamine :
Breaking out !!
#Alkylamine
#nifty
#banknifty
#multibagger
#EquityDynamo
https://t.co/TZnlnLExrl
ALKYLAMINE :
Breaking out !!
#alkylamine
#smallcaps
#midcaps
#multibagger
#nifty
#banknifty
#equitydynamo
Breaking out !!
#Alkylamine
#nifty
#banknifty
#multibagger
#EquityDynamo
https://t.co/TZnlnLExrl
ALKYLAMINE :
— Equity Dynamo (@EquityDynamo) March 17, 2021
Breaking out !! #alkylamine #smallcaps #midcaps #multibagger #nifty #banknifty #equitydynamo pic.twitter.com/UG1vEATIEb
ALKYLAMINE :
Breaking out !!
#alkylamine
#smallcaps
#midcaps
#multibagger
#nifty
#banknifty
#equitydynamo
More from Cdsl
#cdsl now trading at 817 from 789..
More fireworks yet to come above 827 BO
This is power of AOV analysis feature.
More fireworks yet to come above 827 BO
This is power of AOV analysis feature.
#Areaofvalue analysis#CDSL
— SSStockAlerts (@ssstockalerts) May 6, 2021
Buy near 21 SMA support. This stock respects 21 SMA for 84% time. Backtested for last 1 year.
Candle size is getting smaller and volume also less then avg volume.
Any time it can reverse from here.
Help/Supporthttps://t.co/rRCfjf3KIi pic.twitter.com/KGyyAAQ1tV
#PORTFOLIO UPDATE
CDSL
CMP: 1258.55
One of my long term PORTFOLIO STOCK is getting ready for the next phase.
Will be a good point to add more quantity. https://t.co/KaidnjSWpY
CDSL
CMP: 1258.55
One of my long term PORTFOLIO STOCK is getting ready for the next phase.
Will be a good point to add more quantity. https://t.co/KaidnjSWpY
A lot of friends ask for stocks that they can invest for next 5 years. I personally believe and personally invested into
— TECHVESTOR (@AshrafZaman3) May 23, 2021
1. IEX
2 CDSL
3. IRCTC
4. NAZARA TECHNOLOGIES
Please do not take this as an investment recommendation. Also my entry price is lower.#investing pic.twitter.com/vKBLV9u4mL
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.
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.