Book II of #WealthOfNations! It's all about stock! Not the kind you fill with chicken and noodles, but the kind that (according to #AdamSmith) makes commercial society go 'round. (II.intro)
https://t.co/FlxQLGdjbW
#WealthOfTweets #SmithTweets
https://t.co/wi1HtrmBPb
#WealthOfTweets #SmithTweets
1) Use it to raise, make, or buy stuff to sell to others.
2) Use it to improve land, or buy machinery and tools for your business.
(II.i.4–5) #WealthOfTweets #SmithTweets
#WealthOfTweets #SmithTweets
More from @AdamSmithWorks
We have to pause now, because we have to have a whole new tweet thread on #AdamSmith and “savage nations,” because he’s going to keep using this kind of phrase, so we need to talk about it. #WealthOfTweets #SmithTweets
Please know that your friendly SmithTweeters give heavy side-eye to Smith’s use of phrases like “savage nations” and “naked savages” and so on. They are obviously shocking to the modern ear, and they should be. #WealthOfTweets #SmithTweets
“Well, it’s the 18th century, what do you expect?” just isn't a sufficient explanation. #WealthOfTweets #SmithTweets
The 21stC changed from talking about the First World/Third World to talking about developed/developing nations. That’s a good change and a respectful one. The terms we use for countries will continue to change. See:
Probably the best way to think about Smith’s use of the term “savage nations” is to think of it as its own developmental stage on its way to a better set of terms for talking about the differences among nations. https://t.co/2wr7yACEv5 #WealthOfTweets #SmithTweets
Please know that your friendly SmithTweeters give heavy side-eye to Smith’s use of phrases like “savage nations” and “naked savages” and so on. They are obviously shocking to the modern ear, and they should be. #WealthOfTweets #SmithTweets
“Well, it’s the 18th century, what do you expect?” just isn't a sufficient explanation. #WealthOfTweets #SmithTweets
The 21stC changed from talking about the First World/Third World to talking about developed/developing nations. That’s a good change and a respectful one. The terms we use for countries will continue to change. See:
Probably the best way to think about Smith’s use of the term “savage nations” is to think of it as its own developmental stage on its way to a better set of terms for talking about the differences among nations. https://t.co/2wr7yACEv5 #WealthOfTweets #SmithTweets
More from Trading
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.