1. India didn't had it's key players playing like Rahul and kohli. So it was always a pressure situation. Even you not see on face but it lies well within them
2. Big players like Ishant, shami, umesh and Bhuvi were injured
3. Rahane was New captain with very few experience in Captaincy. He only captained 4 matches before it.
4. Gabba was the ground or I would say fortress of Australia where it was unbeaten for past 33 years
5. Paine was Sledging Ashwin in last match
6. India had previously played 6 matches at Gabba and had a record of losing 5 and drawing 1.
7. The bowlers which were bowling had a total of 13 wickets in International test matches whereas Australian bowlers had a combined number of 1200 wicket in tests. These guys managed to take all 20 wickets but Cummins, Hazelwood, Starc and Lyon couldn't.
8. India had many youngsters batting with very few experience like pant, gill, sundar and shardul thakur. Still they scored for team India when it was needed the most
9. Also all great players of past predict the results in Australia's Favour
10. So India although against all the odds against them defeated Australian team in their fortress.

This is all what makes this win so special. ๐Ÿ‡ฎ๐Ÿ‡ณ๐Ÿ…๐Ÿ’™
What a moment ๐Ÿ’™๐Ÿ’™๐Ÿ’™

More from Sport

I don't think people understand the vital difference between a well-rehearsed (and physical) team vs a collection of individuals with no real understanding - new players, makeshift centre-backs, other players out of position. Make do an mend when missing a ton of quality = v.hard


Add fatigue,with less option to rotate, and big effort in 3 away games in previous 9 days. Team lacks height and heft without VvD, Matip, Fabinho, Gomez. Team lacks pace and goals without Jota, Manรฉ. Lacks pace at back without VvD and Gomez. No senior keeper undermines confidence

Team has been disrupted constantly this ssn. Rarely below 6 injuries, often = 10. Thiago a real bonus after months out, but the proper team is not around him. Even Gini looked knackered yesterday. 5th/6th-choice strikers and centre-backs will always be a big drop from 1st choices

Last night was a bit grim, and Brighton were excellent. But it was a strong XI for them, in terms of usual players and in terms of physicality. LFC full of skilful slower little guys right now - lacking the skilful bodyguards and pace. Kabak should help, but he's young and new

You can read Mentality Monsters or Perched for how much I talk about the unity of a team, the practiced understanding from years of intense training together, knowing each others runs and movements. Right now it's a team of semi-strangers and stand-ins.

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.