"Closing the beaches doesn't cost anyone money" - this claim is entirely incorrect. I will now explain why: a thread.

Our economy is compiled from numerous industries that have countless forward and backward linkages with each other. If one is damaged, all are damaged. 1/6

The beach isn't just a piece of sand between sea and land: it is a productive input, a venue, and a reason of existence for numerous businesses. From hotels, to guest houses, to restaurants, to adventure and sport companies, to touring companies: all rely on open beaches. 2/6
Empty hotels, restaurants, and other tourism-related companies that have all lost business because of closed beaches mean no income for them. They cannot pay suppliers, and other industries that rely on them also don't make money: airlines, tour companies, car rentals etc. 3/6
This means owners and employees on paycuts and layoffs who cannot pay their own bills, causing a further knock-on effect in other industries not directly connected with tourism or hospitality at all. Suppliers and clients are equally out of pocket. 4/6
The economy is a vibrant, complex creature: you cannot shut individual organs down and expect it to function. In fact, there are significant and severe consequences for this type of governmental meddling in a fragile and complicated ecosystem. 5/6
Thus, you cannot just close the beaches and think people aren't deeply and severely impacted by it. It leads to massive losses in income, inability to service costs, unemployment, and a debilitating multiplier effect felt across numerous industries. 6/6

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.