STRANGE PICS THREAD.

Yep, the weird stuff.

More from Fun

A thread on @Dream, his friends, Minecraft, insane Twitter engagement, and more:

Dream & friends' (@GeorgeNotFound, @tommyinnit, @Quackity, @TubboLive, @WilburSoot, etc) meteoric rise and the massive return of Minecraft has been one of the most amazing gaming stories this year.


1/ What do Dream and crew get so right?

On the surface, it's clear that they show the power of good storytelling and each of our desires to "hang out" with a group of friends that are having fun.

(image @Animagician_)


2/ This remains one of, if not the most important draws for great parasocial content -- whether it be Seinfeld, @DavidDobrik's vlogs, or Dream SMP content, the same is true:

We want to feel a little less alone and spend time in the worlds of these friends we know so much about.

3/ Watching this new wave of superstars take over YouTube / Twitch / Twitter gaming cultures has been incredible and bizarre.

Check the replies and engagement


4/ Dream speaks to the underrated and remarkable nature of Minecraft, too. In its 9th year, the game continues to dominate. Why?

Accessible, multi-platform, wide appeal? Sure - but more importantly: it is infinitely extendable. It's a creator's perfect sandbox. (image @SipoverS)

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.