2/19
The last Hindu king of Pakistan.
The name Amarkot is known to all in our subcontinent as the birthplace of Emperor Akbar. When Humayun was fleeing from Sher Shah, Rana Prasad of Amarkot sheltered him and this is where Emperor Akbar was born.
#Thread
1/19
@talesofBharat
2/19
But another reason why the name of this Amarkot is inextricably linked with the history of the subcontinent is the partition of the country.
Sodha is the family name of the Maharajas of..
3/19
4/19
After the capture of the fort by the
5/19
6/19
In 1946,Jawaharlal Nehru went to Amarkot to invite the then Maharaja Rana Arjun Singh to join the Congress. At that time Amarkot had a population of 12,000 Hindus which was 90% of the
7/19
8/19
In fact, the reason behind Rana joining the Muslim League was different. The Maharaja of Jodhpur had a perpetual hostile relationship with the Rana of Amarkot from the twelfth century onwards.
9/19
10/19
During the war on the western battlefield in 1971,
11/19
12/19
Rana Chander Singh Sodha is a very conservative person personally and he even adheres to the caste system very well even though he maintained perfect
Harmony
13/19
14/19
15/19
16/19
His son Hamir Singh Sodha was also the Minister of Agriculture in the Sindh Provincial Council and is currently the Member of Parliament for Pakistan.
17/19
More from All
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.