Must say, Modi Sarkar had brilliantly so far in the face of extreme provocation.
Do u think Delhi Police is so useless that they can't stop a few hundred people from entering Red Fort? Not even a single body has fallen so far
(1) #FarmersProstests
More from India
Many are upset at the bus attacks & Red Fort events during #FarmersProtest.
But have you paused to think what has brought about this situation? While magnifying impulsive actions by some protesters, do you miss to see State's systematic violence and erosion of rule of law?
If you are a believer in Constitution and legitimate processes, then the manner in which the Centre pushed the #FarmLaws & handled the #FarmersProstests should leave you distressed.
First, Centre brings these laws as Ordinances on subjects which are apparently in state list, through a colorable use of concurrent list. Principle of federalism negated, at least in spirit, if not in letter.
Then, bills are passed in Parliament without effective discussions.
No one can say for sure if the bills were actually passed in vote in Rajya Sabha. The whole process was brazenly dubious. The live telecast was stopped amid protests. Really shameful events.
So, lawful processes to address dissent undermined.
#FarmersProtest
#FarmLaws
Then some farm groups approach the Supreme Court raising some pertinent questions on constitutionality. Instead of considering legality, court ventures into political thicket by attempting mediation, that too with a hand-picked committee having only members supporting #FarmLaws .
But have you paused to think what has brought about this situation? While magnifying impulsive actions by some protesters, do you miss to see State's systematic violence and erosion of rule of law?
How it started: How it's going: pic.twitter.com/bwkqp3uYQu
— Manu Sebastian (@manuvichar) January 26, 2021
If you are a believer in Constitution and legitimate processes, then the manner in which the Centre pushed the #FarmLaws & handled the #FarmersProstests should leave you distressed.
First, Centre brings these laws as Ordinances on subjects which are apparently in state list, through a colorable use of concurrent list. Principle of federalism negated, at least in spirit, if not in letter.
Then, bills are passed in Parliament without effective discussions.
No one can say for sure if the bills were actually passed in vote in Rajya Sabha. The whole process was brazenly dubious. The live telecast was stopped amid protests. Really shameful events.
So, lawful processes to address dissent undermined.
#FarmersProtest
#FarmLaws
Then some farm groups approach the Supreme Court raising some pertinent questions on constitutionality. Instead of considering legality, court ventures into political thicket by attempting mediation, that too with a hand-picked committee having only members supporting #FarmLaws .
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.