HN user

hongsy

666 karma
Posts13
Comments22
View on HN

In refining 0x3890 : 0xE193C5 (Labrador) in 00h 06m 29s 468ms I have brought glory to the company. Praise Kier. 7⃣3⃣9⃣9⃣6⃣ 4⃣4⃣8⃣1⃣5⃣ 4⃣3⃣5⃣4⃣4⃣ 0⃣4⃣7⃣4⃣3⃣ 5⃣8⃣1⃣5⃣0⃣ #mdrlumon #severance lumon-industries.com

Reminded me of this https://en.wikipedia.org/wiki/Impossible_trinity

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 policy

What really grates at people’s nerves?

Uncertainty. 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...

i convinced myself that commits are snapshots by doing the following:

    # 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)

i convinced myself that commits are snapshots by doing the following:

    # 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)

i convinced myself that commits are snapshots by doing the following:

    # 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)

If commits are snapshots:

- 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?