There has been considerable speculation by serious researchers into the Bronze/Iron Age cultures who could have produced the itihaasas. While not being a pursuit into the exact provenance.

Krishna Kumar published a detailed analysis in BORI 1992.....(1/n)

The earliest culture marked by a very specific profusion of weapons is the Ochre Coloured Pottery (OCP) culture in the Upper Ganga-Yamuna Doab.

Flat, bar & shouldered celts, double edged axe, hatchet, rings, antennae swords, hooked swords and spearheads, barbed harpoons...(2/n)
Krishna Kumar provides a detailed characterisation of the economy of the OCP people...(3/n)
The OCP culture has its origins in the middle of the 3rd millennium BCE in the chalcolithic Ganeshwara-Jodhpura culture. (Deepak Nair, 2012)

(4/n)....
Krishna Kumar points out the similarity of weapons mentioned in the Ramayana to those of the archaeological remains of the OCP culture. (5/n)
Copper Hoard/OCP culture type weapons have proliferated throughout India in the archaeo record.

Krishna Kumar therefore assesses a fit between the culture that might have produced the Ramayana and the archaeo-record. (6/n)
Since Krishna Kumar published his weapon/archaeo/textual fitting paper in 1992, several events have overtaken us.

The finding of a grave buried chariot at Sinauli (OCP culture) has led to renewed discussions in the Indian archaeological community. (7/n)
The world of the OCP was different from the Harappan world. This was a war-making culture that was technologically sufficient in weapon making.

The contrast with Harappans, who seemed to have exclusively concentrated on trade/urbanism, could not be greater. (8/n)
If viewed correctly, we see a concordance between the events of the Ramayana with a specific archaeo-attested culture that was dominant in weaponry. The time range is 2000-1500 BCE. The North-South progression that is evident in the OCP spread.

(n/n)

More from All

ChatGPT is a phenomenal AI Tool.

But don't limit yourself to just ChatGPT.

Here're 8 AI-powered tools you should try in 2023:

1. KaiberAI

@KaiberAI helps you generate beautiful videos in minutes.

Transform your ideas into the visual stories of your dreams with this Amazing Tool.

New features:
1. Upload your custom music
2. Prompt Templates
3. Camera Movements:

Check here

https://t.co/ivnDRf628L


2. @tldview TLDV

Best ChatGPT Alternative for meetings.

Make your meetings 10X more productive with this amazing tool.

Try it now:

https://t.co/vOy3sS4QfJ


3. ComposeAI

Use ComposeAI for generating any text using AI.

It’s will help you write better content in seconds.

Try it here:

https://t.co/ksj5aop5ZI


4. Browser AI

Use this AI tool to extract and monitor data from any website.

Train a robot in 2 minutes to do your work.

No coding required.

https://t.co/nNiawtUMyO

You May Also Like

12 TRADING SETUPS which experts are using.

These setups I found from the following 4 accounts:

1. @Pathik_Trader
2. @sourabhsiso19
3. @ITRADE191
4. @DillikiBiili

Share for the benefit of everyone.

Here are the setups from @Pathik_Trader Sir first.

1. Open Drive (Intraday Setup explained)


Bactesting results of Open Drive


2. Two Price Action setups to get good long side trade for intraday.

1. PDC Acts as Support
2. PDH Acts as


Example of PDC/PDH Setup given
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.