#Inflation in #Eurozone remains high , uncomfortable for #ECB & #FED also has to take notice
Should strengthen #Euro & weaken #USD on immediate reaction, pushing commodity prices higher
#CrudeOil #Metals #OOTT
![](https://pbs.twimg.com/media/Fabsz1KaIAAo30I.png)
More from 🙏 I Pray to the Lotus Feet of Shri Krishna 🕉️
More from Screeners
May please read the attached tweet once again for a key LEARNING
USDINR - a breakout that will not bode well for the equities
78+ https://t.co/AWqZxF5B1L
USDINR - a breakout that will not bode well for the equities
78+ https://t.co/AWqZxF5B1L
![](https://pbs.twimg.com/media/FU5TSOOUYAIj03f.png)
Can you anticipate a breakout? Yes
— The_Chartist \U0001f4c8 (@charts_zone) June 10, 2022
the attached tweet.
now the chart is for USDINR https://t.co/Vb2wKaCvTB pic.twitter.com/INo0GC4fGY
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
![](https://pbs.twimg.com/media/DrIk2JhU8AAjf_m.jpg)
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
![](https://pbs.twimg.com/media/DrIk3TjU0AAhf3D.jpg)
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.