@_CreatingWealth @suru27 But I guess Kovai caters to the lower end of the spectrum so it's impact is much limited and perhaps be a beneficiary.

More from Valuation

June's research paper: Intangible Value ✨

Can value investing strategies be improved by adding intangible assets?
👾 The Asset-Light Economy
🔮 The Dark Matter of Finance
🏰 Intangible Moats
📉 The Disruption of Value
👨‍🎓 Fixing the "Value Factor"

(Not investment advice)

🧵

(0/10) Full paper here 📘

Blog
https://t.co/omtrn9kfvt


(1/10) The Asset-Light Economy 👾

“The four largest companies today by market value do not need any net tangible assets. They are not like AT&T, GM, or Exxon Mobil, requiring lots of capital to produce earnings. We have become an asset-light economy."

- Warren Buffett


(2/10) The End of Accounting 🧮

“The constant rise in the importance of intangibles in companies’ performance and value creation, yet suppressed by accounting and reporting practices, renders financial information increasingly irrelevant.”

- Baruch Lev and Feng Gu


(3/10) The Dark Matter of Finance 🔮

While intangible matter holds the financial universe together, it is not visible to the naked eye. Unstructured data contains info on intangibles but is large, noisy, and resistant to standard statistical analysis.

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.