#tradingtips
#EndofDayScans #free scans
Bullish Scan for 2nd Day Continuation
https://t.co/NywR2hxKhM
Bearish Scan for 2nd Day Continuation
https://t.co/AfNLATYnGm
Save them, Can find good plays using them for next day
I gave many winners here using same 🙏
More from Screeners
Most of the indices are entering oversold territories
Take small cap index for example
Whenever Monthly RSI is below or around 40, the index bottoms out
We are getting there.
If I had 50% cash, I would have deployed some in beaten down stocks where earnings growth is intact. https://t.co/t5WwgH1V5o
Take small cap index for example
Whenever Monthly RSI is below or around 40, the index bottoms out
We are getting there.
If I had 50% cash, I would have deployed some in beaten down stocks where earnings growth is intact. https://t.co/t5WwgH1V5o
I have more than 50% cash but still worried if this is a good time. Will invest 20% by EoY
— Tamil Metaverse (@TamilMetaverse) June 21, 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.