10 Stoic Quotes On Ancient Knowledge To Motivate You

1.

2.
3.
4.
5.
6.
7.
8.
9.
10.
Lastly,
If this thread was able to add 1% value to your life,

A RT to the first tweet of the thread will be appreciated.

To make sure that you don't miss out on my upcoming threads,

Follow @JackedAecus

Thanks for reading.https://t.co/fuBEhmwpIL
⚠️Attention⚠️

We all have 24 hours in a day.

And it completely depends upon us whether we waste it scrolling through social media...

Or build some real stuff in the real world.

Start your life as a creator on Twitter.

Get your free guide here 👇🏻

https://t.co/HAg50hkkg5

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.