The response of Western pagans/polytheists to ongoing Muslim and Christian aggression against Hindus in India is truly disgraceful. Daily these pagans whine and whimper about Christian hegemony and constantly embellish their oppression in the West. 1/5

Meanwhile, Hindus in India witness violent attacks on temples, icons, and worshipers. They face a barrage of state, media, and academic misinformation—both in the West and even in India--about their religions and the threats to them. 2/5
When Hindus mobilize to resist these attacks of various forms, the cowardly, mewling pagans wrap it up with and condemn it as “fascism.” Once again these pagans reveal themselves spineless in the face of real anti-religious action. 3/5
Instead of solidarity with one of the oldest, continuously-practiced indigenous religions in the world, they aid and abet the forces of disorder, dissolution, and godlessness. They are anti-dharma; there is no other way to put it. 4/5
If they can’t stand with dharma, with Hindus and Hinduism, then there is little hope that they can maintain and carry forth their own traditions here. 5/5

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.