https://francisduvivier.github.io/eternal-struggle-with-spee...
Code: https://github.com/francisduvivier/eternal-struggle-with-spe...
[1] https://francisduvivier.github.io/eternal-struggle-with-spee...
1. cloudy; overcast; gloomy
2. hidden; secret
3. negative [of electrical charge]
4. the Moon
5. shade; shadow
6. north of a mountain or south of a river
7. back side
8. of the nether world; of ghosts
9. (philosophy) "female" principle; yin in yin-yang
10. in intaglio
11. treacherous; deceitful; cheating
12. (dialectal) to deceive; to trick; to trap
13. (Chinese phonetics, of a syllable) open; not having a consonant coda
14. (Cantonese) bangs; fringe
15. genitalia (of humans)
16. a surname
The one (American) person I know who has 陰 as a surname reports that Chinese people are often shocked at her surname upon meeting her. I think it might be a bit like having the surname Death in English (https://www.ancestry.com/last-name-meaning/death?geo-lang=en...).
That is to say, black kind of does mean "bad" here, in the popular conception anyway. Taoism and Buddhism promote a worldview that sees birth and death, creation and destruction, as neither good nor bad, simply inseparable parts of a larger whole. But most everyday people try to avoid darkness, death, destruction, cloudiness, gloominess, shadows, ghosts, treachery, traps, and so on, most of the time. It's more that Taoism teaches that this attempt is foolish.
Not all the senses are unpopular; plenty of people like human genitalia, the Moon, and intaglio, and the shady side of a river can be nicer when it's hot out.
Very on brand, it does not work correctly. I can turn the speed up but not back down again.
Now to be honest I saw this bug, but I decided to just release it anyways because I also already had the v2 in the works which incidentally already had this issue fixed.
If you go to 64.00×, it can't slow back anymore.
https://francisduvivier.github.io/eternal-struggle-with-spee...
Someone put this into an AI super duper thinking max edition, sprinkle some MCP on top and see what happens lol
Still buggy. If you increase the ball size and increase the speed, the whole thing goes black/white in 10 seconds.
Isn’t that the main characteristic of vibe-coded code anyway?
Running 100x for some moments, the white part got pincer maneuvered by the black and I ended up with the whole circle becoming black. Don't know what to think of that lol
(That assumes that the simulation is randomized of course, which doesn't seem to be the case for the one in the link posted here.)
On a phone it doesn’t seem to trigger unless I changed the background so I spent a minute just staring at the symbol without anything happening lol :D
function keyPressed() {
if (key === 'p') SHOW_POINTS = !SHOW_POINTS;
}You had a bunch of critters scattered around the map trying to get home and you had to make paths for them while stopping your opponent from getting their critters home.
anyone willing to provide a math-proof like argument on why the shape seem to stick to the YY curve indefinitely as the "eternal" name suggests?
Should it always be this way or is there at least one bad initial bouncing configuration for which chaos can take place and we loose the YY curve?
Does not seem that obvious to me.
I'm not even a dimwitted individual with an advanced degree in hyperbolic topology, but I can see what's happening intuitively. When one of the balls makes an indent large enough, that indent focusses the bounce from the circular edge which reinforces the indent further. This leads to a semi-stable shape where one of the balls is bouncing around a horseshoe and the other in a tunnel. However, if one side of the horseshoe becomes pinched small enough that ball is less likely to enter, that side of get eliminated, and you have a yin-yang.
More simply, the round edge seems to encourage tunnelling, and any asymmetry in the tunnelling is yin-yang-ish.
For obvious reasons it tends to stay half white half black (if one half gets smaller its ball will bounce faster) but the shape and its orientation varies randomly.
https://d6f9e5179057.s3.us-west-2.amazonaws.com/Screenshot%2...
data.whiteBall.v.x = 5; data.whiteBall.v.y = 5;
data.blackBall.v.y = 5; data.blackBall.v.x = 5;
data.whiteBall.v.x = data.whiteBall.v.y = data.blackBall.v.y = data.blackBall.v.x = 10;
['whiteBall', 'blackBall'].forEach(color => { data[color].v.x *= 5; data[color].v.y *= 5 });
In dev console :)
Not seen one of these tables with two balls in... You'd probably need quite a lot of height to offset the linear sliders so didn't collide with each other.
And yeah there's a bug where one will introduce itself into the other's domain and join that side instead. Very life-like :)
It would be better if there was only 1 kind of edge instead of 2.
I refer to the broken edge and the circle edge.
