More from Shubham Mishra🇮🇳⚡
GNFC
Channel Update
I know many are holding it thats why posting this..I dont have any personal positions https://t.co/csDKE29Cp5
GNFC
Decision time coming soon👇
Channel Update
I know many are holding it thats why posting this..I dont have any personal positions https://t.co/csDKE29Cp5
#GNFC
— Shubham Mishra\U0001f1ee\U0001f1f3\u26a1 (@shubhfin) April 25, 2022
Coming back inside the channel https://t.co/5LRx3TrAjP pic.twitter.com/0Z6r5g3bks
GNFC
Decision time coming soon👇
More from Tataelxsi
Tata Elxsi - IH&S continuation breakout done.
Target opened as per the pattern is 8900 https://t.co/nRqYqPnPB3
Target opened as per the pattern is 8900 https://t.co/nRqYqPnPB3
Tata Elxsi - I waited for the trigger today but to no avail. The setup is still the best with price consolidating right in the RS zone. Waiting for the breakout till then no action. pic.twitter.com/LnOPswWgAp
— The_Chartist \U0001f4c8 (@charts_zone) March 16, 2022
Tata Elxsi - DTB active after close above 4527.75 https://t.co/rO4f8hkPFF
Tata Elxsi - Daily I track this chart and waiting for a big kill in this. You have to act like a cheetah sometimes waiting for the weakest hit.
— The_Chartist \U0001f4c8 (@nison_steve) August 10, 2021
There are times when you must sit patiently to catch your prey. pic.twitter.com/CRoBHIetHE
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.