Draw a square around Einstein's face. Call the side length of the square a and the area of the square A. We have A=a^2. Einstein takes up some portion p < 1 of that area, so Einstein has area E = pA. Now we scale the whole thing by factor f. So the new square has side lengths fa, and thus area A' = (fa)^2 = f^2×a^2 = f^2×A. Since the relative portion the face takes up doesn't change with scaling, the face now has size pA' = p×f^2×A = f^2 × pA = f^2 E.
Does that help or was that not the part you were missing?
No, that part is fine: I'm happy with the fact that it works with arbitrary shapes. What bothers me is that the area on the hypotenuse is equal to the sum of the areas on the other two sides, when the triangle has a right angle.
This somewhat like saying that I'm troubled by the fact that 1+1=2, I know. But that's a potentially distracting sidetrack, let's not get into that one.
What are these called / do you have a source for that? I never heard of that and a quick Google didn't turn up anything except for changes planned for 2028.
Which old times are you referring to / what are "sensible" names?
I thought about it and I don't know what a better name would be. Off the top of my Head, I know Perforce, BitWarden, Subversion, fossil and git. And then the abbreviations CVS, RCS and SVN.
I don't just mean version control systems, but since you mentioned them: CVS (concurrent version system), rcs (revision control system) and subversion all seem fairly descriptive to me?
That may be the reason in other countries, but parent-poster talks about an intersection in California, and as far as I can tell US regulations require symmetric (unbiased) low-beams, and high-beams are usually symmetric everywhere.
> When installed on a motor vehicle, the headlamps (or parts thereof) that provide the lower beam must be of the same type and provide a symmetrical effective projected luminous lens area when illuminated.
> One repo uses `master` but a subtree uses `main`. If you make a mistake and checkout `main` you end up clobbering your whole working tree with the subtree.
If you replace checkout with switch/restore, that foot gun goes away.
A very effective solution for that is a well-configured shell. IF you summarize the state of the repo in the prompt, it is always visible while typing a command.
Does that help or was that not the part you were missing?