Everything that's wrong with tech journalism, in one tweet.

Allow me to go on a little rant here.

Technology is becoming pervasive in our lives. Critical components of our world are increasingly becoming more dependent on the internet. We're putting critical infrastructure, and home appliances online.
Larger and larger swaths on the information/media ecosystem are more and more dependent on Google and Facebook.

Nations have already successfully swayed other nations' elections or at least popular beliefs with mediocre disinformation campaigns.
Now more than ever we can't afford to have a tech press that just waits for these multi-billion $ giants to give them access and embargoes in exchange for puff pieces.

We need critical technology reporting. We need 5,000-word investigative pieces, not 5,000-word iPhone reviews.
Let's all be better because no one should care more about how the new iPhone camera is as opposed to Amazon or Tesla's shitty labor practices. Or the rampant sexism of Silicon Valley.

More from All

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.