666 karma · joined June 30, 2017
The impossible trinity (also known as the impossible trilemma or the Unholy Trinity) is a concept in international economics and international political economy which states that it is impossible to have all three of the following at the same time:
- a fixed foreign exchange rate
- free capital movement (absence of capital controls)
- an independent monetary policyUncertainty. Not knowing when you will end up testing positive and be whisked off by one of the commissar’s white costumed goon squads in the middle of the night. If you don’t agree, that’s when they typically come, like the NKVD secret police back in the Soviet Union. And not knowing what will happen to your children, your elderly parents and your pets if / when that day comes.
https://austrianchina.substack.com/p/tragedy-and-hope-in-sha...
Do you have a source for this?
# generate a 100M text file
base64 -b 76 /dev/urandom | head -c 100000000 > file.txt
git add . && git commit -m "1"
# remove first line and add a new line to bottom
tail -n +2 file.txt > tmp && rm file.txt && mv tmp file.txt && base64 -b 76 /dev/urandom | head -n 1 >> file.txt
git add . && git commit -m "2"
# repeat
tail -n +2 file.txt > tmp && rm file.txt && mv tmp file.txt && base64 -b 76 /dev/urandom | head -n 1 >> file.txt
git add . && git commit -m "3"
...
du -sh . # a very big folder
each of the commits are almost 80M big in the git folder. if you run `du -h .` you can see how git stores each object individually (80M big) # generate a 100M text file
base64 -b 76 /dev/urandom | head -c 100000000 > file.txt
git add . && git commit -m "1"
# remove first line and add a new line to bottom
tail -n +2 file.txt > tmp && rm file.txt && mv tmp file.txt && base64 -b 76 /dev/urandom | head -n 1 >> file.txt
git add . && git commit -m "2"
# repeat
tail -n +2 file.txt > tmp && rm file.txt && mv tmp file.txt && base64 -b 76 /dev/urandom | head -n 1 >> file.txt
git add . && git commit -m "3"
...
du -sh . # a very big folder
each of the commits are almost 80M big in the git folder. if you run `du -h .` you can see how git stores each object individually (80M big) # generate a 100M text file
base64 -b 76 /dev/urandom | head -c 100000000 > file.txt
git add . && git commit -m "1"
# remove first line and add a new line to bottom
tail -n +2 file.txt > tmp && rm file.txt && mv tmp file.txt && base64 -b 76 /dev/urandom | head -n 1 >> file.txt
git add . && git commit -m "2"
# repeat
tail -n +2 file.txt > tmp && rm file.txt && mv tmp file.txt && base64 -b 76 /dev/urandom | head -n 1 >> file.txt
git add . && git commit -m "3"
...
du -sh . # a very big folder
each of the commits are almost 80M big in the git folder. if you run `du -h .` you can see how git stores each object individually (80M big)- say i have a repo with one file, a big 100MB csv with millions of lines.
- i change one line in the CSV for one commit.
- repeat multiple times in many many commits.
- how big will the repo be?