#IRCTC futures on short term charts , looks like welcoming the new railway minister 🙂
Charts on 0.15% and 0.25%
More from DTBhat
More from Irctc
irctc
approching upper trendine , might took a small pause or need to break resistance with good volumes
target was 2900 , made high 2897 , with just 3 points short.
booking some positions as reached near resistance , will add near supportive trendline,
holding rest for 3600 https://t.co/2H0myGPgu5
approching upper trendine , might took a small pause or need to break resistance with good volumes
target was 2900 , made high 2897 , with just 3 points short.
booking some positions as reached near resistance , will add near supportive trendline,
holding rest for 3600 https://t.co/2H0myGPgu5
Itctc
— Vibhor Varshney (@nakulvibhor) September 2, 2021
Entered 2800 \u2705
Heading towards 2900 target
Then 3600
Holding personally in folio \U0001f44d https://t.co/jd2OOQTSLs
#IRCTC-6375
4.618%(6406) Sustain rise above this
level upside #Fibonacci extension
6.857% 9135
#Probability
4.618%(6406) Sustain rise above this
level upside #Fibonacci extension
6.857% 9135
#Probability
#IRCTC -2351
— Waves_Perception(Dinesh Patel) \u092e\u0948\u0902Schedule Tribes) (@idineshptl) July 16, 2021
Now above 1.272% (2325)
Next 1.618%
Than 2.618% ...
Near term Base case 1987.#Probability pic.twitter.com/MJad8gnmWz
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.