Chinese painting Updated +Created
Hawaii Updated +Created
Illinois Updated +Created
Qing dynasty Updated +Created
Reduced Planck constant Updated +Created
San Francisco Bay Updated +Created
AI accelerator Updated +Created
Video 1.
The Coming AI Chip Boom by Asianometry (2022)
Source.
Curl (mathematics) Updated +Created
Points in the direction in which a wind spinner spins fastest.
Retrovirus Updated +Created
Integrates its RNA genome into the host genome.
Sounds complicated! The advantage is likely as in HIV: once inside the cell, it can remain hidden far away from the cell surface, but still infections.
Ribosome Updated +Created
Video 1.
Ribosome by WEHImovies (2017)
Source. The should slow that down a bit.
Video 2.
mRNA Translation by DNA Learning Center (2010)
Source.
Richard Henderson (biologist) Updated +Created
Roche Biochemical Pathways Updated +Created
TODO human presumably?
I don't think it has any advantage over KEGG however, besides historical interest? Maybe slightly more manual layout and so more beautiful?
James Somers (rightly) likes to point to it as a "biology is awesome" thing.
Rockefeller family Updated +Created
They were basically a Microsoft of their century. A little less monopolistic perhaps as countries believed they should own they natural resources, unlike their data.
RPG Maker Updated +Created
The one true game engine!
Video 1.
Reviewing a Bunch of RPG Maker Games by Majuular (2022)
Source.
gcc CLI option Updated +Created
Git command Updated +Created
Git design rationale Updated +Created
The fundamental insight of Git design is: a SHA represents not only current state, but also the full history due to the Merkle tree implementation, see notably:
This makes it so that you will always notice if you are overwriting history on the remote, even if you are developing from two separate local computers (or more commonly, two people in two different local computers) and therefore will never lose any work accidentally.
It is very hard to achieve that without the Merkle tree.
Consider for example the most naive approach possible of marking versions with consecutive numbers:
  • Local 1:
  • Local 2:
    • 0: root commit
    • 1: commit 1
    • 2: commit 2 by local 2
    • 3: commit 3 by local 2
  • Remote
If Local 1 were to push to Remote first, how could Local 2 notice that when it tries to push itself? The navie method of just checking: "does Remote have commit "2"" does not work, because Local 2 has a different version of commit 2 than local 1.
GNU package Updated +Created
Google acquisition Updated +Created

Unlisted articles are being shown, click here to show only listed articles.