APOLLOPIPE
Double Top Buy triggered above 1608.64 daily close on 1% Box Size chart. https://t.co/7jxOpBHGUO

APOLLOPIPE
— Saket Reddy (@saketreddy) July 26, 2021
Double Top Buy & T20 Pattern - Bullish above 1204.85 daily close on 3% Box Size chart. pic.twitter.com/009A5IXJeP
More from Saket Reddy
More from Aplapollo
Three interesting players in the pipes industry have been covered on the SOIC platform! 🎉
Apollo Pipes was highly requested company after we released Prince Pipes analysis.
Hope this matches the expectation of the community. 🙏
Apollo Pipes was highly requested company after we released Prince Pipes analysis.
Hope this matches the expectation of the community. 🙏
Another Superb Blog by @badola_arjun . This time on Apollo Pipes \U0001f3d7\ufe0f\U0001f3d7\ufe0f
— Intrinsic Compounding (@soicfinance) September 8, 2021
This completes our PVC/CPVC pipes industry analysis. Done with Astral,Prince and Apollo \U0001f600
Link to read\U0001f517: https://t.co/Ib40q9Fg3g pic.twitter.com/TlN1Urgp01
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.