https://t.co/2UzelIpQa7
Due to @asadowaisi's political expansion, question asked nowadays is whether or not Muslims voting for AIMIM is a communal phenomenon
But nobody has answers for
Majoritarian politics, which already divides voters along religious identity
Ajay
https://t.co/2UzelIpQa7
https://t.co/2UzelIpQa7
https://t.co/2UzelIpQa7
https://t.co/2UzelIpQa7
https://t.co/2UzelIpQa7
https://t.co/2UzelIpQa7
https://t.co/2UzelIpQa7
The point that Muslims have and do vote for non-Muslim parties gets waylaid. Besides, Hindus could legitimately counter that they, too, vote for non-BJP parties.
It could also be argued that the @aimim_national looks sectarian because Hindus would not vote for a party that is committed to uniting Muslim.
https://t.co/2UzelIpQa7
Muslims could well wonder why secular parties have not come together to defeat the BJP and why doing so is seen as a concern of only the Muslims and @aimim_national
https://t.co/2UzelIpQa7
What is the track-record of the AIMIM in bringing about positive changes in the lives of Muslims in Hyderabad, leave alone Telangana?
https://t.co/2UzelIpQa7
More from India
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.