Inaugural outfits as gemstones: a thread

MVP Kamala Harris as Tanzanite

FLOTUS Dr. Jill Biden as Aquamarine (a variety of Beryl)
FLOTUS44 Michelle Obama as Rhodolite (a variety of pyrope garnet)
Amy Klobuchar as yellow Topaz
Bernie Sanders as gray jasper
Doug Emhoff as Onyx
POTUS Joe Biden as Sodalite
POTUS44 Barack Obama as Salt and Pepper Diamond

(fun fact: s&p diamonds are just diamonds with graphite inclusions)
Elizabeth Warren as pink and blue Tourmaline
Meena Harris as Emerald (also a variety of Beryl)
Hillary Clinton as purple Zircon
Amanda Gorman as Wulfenite
Mike Pence as Coprolite (IYKYK)
P.S. if you're able please donate to your local food bank or Feeding America
P.P.S. If you came here to wokescold you owe $5 to your local mutual aid network

More from Fun

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

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

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.