Been working on something..

Follow the missing letters from @LLinWood

More from Fun

You May Also Like

#Bookmark this

The full story of || Dhruv ||

We’ll see How Dhruv occupied a fixed position in the northern sky?

I repeat “Untold Unsung now Unearthed”

Go through entire thread carefully.

OM NAMO BHAGWATE VAASUDEVAAY

RT & spread the knowledge.
Any questions use #AskPratz


.... continuing from previous thread/story

O prince! Thus concentrate on that omnipotent eternal Lord with the mantra - ‘OM NAMO BHAGWATE VAASUDEVAAY’ .

https://t.co/H62ehDT3ix


The prince Dhruv greeted the sages and continued on his journey. At last, he reached a beautiful forest Madhuvan on the bank of the river Yamuna. It was the same forest, which was later occupied by a demon Madhu.


Shatrughana, the youngest brother of Sri Rama had killed demon Lavan, son of Madhu in the same forest & founded the township of Mathura. In the same forest, prince Dhruv decided to carry out his penance. As per the dictate of the sages, he began to recite the mantra continuously


Very soon, the earth began to move because of Dhruv’s severe penance. Even the seat of Indra could not remain stable. A stampede resulted among the gods. The gods then hatched a conspiracy to disturb the penance.
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.