India has always been a paradise of art. Not jus coz i am born here, being an Artist i connect to this land even more. The only thing that saddens my heart is we do not value our own treasures.
#thread
#TalesofIndia


This one has two gold peacocks with ruby eyes. And coral beads hanging across.

This one was sold at Sotheby's

These are silver combs and you will be astonished to know they are hollow from inside to contain perfumes. Can u spot the silver knobs at the end? They are engraved with the face of a warrior & his consort.


Residing in the Museum of Fine Arts Houston is a divine Radha Krishna carved comb.
On this ivory comb you can see Krishna & radha tending to 4 cows beneath the pedestal while other consorts holding parasol, fly whisk fan & sceptre

These 2 Krishna combs are from Madurai are now a collection of Susan L Beningson.

Cute na? 😍😍


That is when combs started to look like this parcel-gilt silver peacock comb. It was made in Northern India in the early 20th Century.

To pre-Colonial Indians,there was no association of women with sin,no Eve or snake or apple.However, the British, especially xtian missionaries,were horrified at temple walls decorated with “much immodest,heathen-style fornication & other abominations.”
More from History
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.