More from Fun
So I got out some CF cards and noticed something odd about this one. Do you see the weirdness?
How the fuck is a CF card "USB Enabled"?
So CF cards are a weird beast that act as either a PCMCIA card or an ATA/IDE card depending on a mode pin.
They're definitely not USB.
And it's not like that weird SanDisk card I have which you can fold in half and plug it in as a USB device.
It turns out the reason for "USB Enabled" is because it's a Lexar drive from the jumpSHOT era.
This is a normal CF card in most cases, you can use it in normal CF card readers and such

How the fuck is a CF card "USB Enabled"?

So CF cards are a weird beast that act as either a PCMCIA card or an ATA/IDE card depending on a mode pin.
They're definitely not USB.
And it's not like that weird SanDisk card I have which you can fold in half and plug it in as a USB device.
Flip it over, bend it in half, and now you can plug your SD card right into a USB port pic.twitter.com/jeBefP2xU1
— foone (@Foone) May 2, 2020
It turns out the reason for "USB Enabled" is because it's a Lexar drive from the jumpSHOT era.
This is a normal CF card in most cases, you can use it in normal CF card readers and such
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.