#Gold$-1763
Daily chart ...more downside likely if sustain below 1763$
#Probability
More from MaRkET WaVES (DINESH PATEL ) Stock Market FARMER
#IEX -393
Objective is to move higher towards
3.618% - 4.236% and 4.618%
#Probability
Objective is to move higher towards
3.618% - 4.236% and 4.618%
#Probability
#IEX
— MaRkET WaVES (DINESH PATEL ) Stock Market FARMER (@idineshptl) April 20, 2021
On sustain rise above 347 upside shown in chart up to 4.618%(521)
And 6.857%(718).
View valid till 233 not violated. @UdayJad39389920 pic.twitter.com/I2MoPlwXRW
More from Gold
Last Akshay Tritiya, had written the below thread 🧵 on which is the best way to buy gold, Physical, Digital, ETF or Sovereign Gold Bond and why?
Do re-tweet and help us educate more retail investors
#investing
Do re-tweet and help us educate more retail investors
#investing
What better day to discuss Gold, isn\u2019t it?
— Kirtan A Shah (@KirtanShahCFP) November 13, 2020
Topic - Physical Gold v/s Digital Gold v/s Gold ETF v/s Sovereign Gold Bond (SGB)
(Thread) \u2013 DO RE-TWEET FOR A LARGER REACH :)
(1/n)
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.