francisduvivier
9 days ago
Some people here were asking for it so I quickly vibe forked a speed control slider for farming some karma here on Hacker News:
https://francisduvivier.github.io/eternal-struggle-with-spee...
Code: https://github.com/francisduvivier/eternal-struggle-with-spe...
wvbdmp
9 days ago
Not to alarm anyone, but when I ran this, the black ball eventually joined the dark side and the whole thing ended up black. I’m sure this doesn’t mean anything for the greater universe.
soneca
9 days ago
This happened to me in the original site. I think it happens when the white and black balls collide at the exact same spot of the border.
temp0826
9 days ago
A little matter-antimatter asymmetry never hurt anyone
nialv7
9 days ago
black-white here doesn't mean bad-good. they just mean opposites, different aspects of things. I think wikipedia does a pretty good job explaining it: https://en.wikipedia.org/wiki/Yin_and_yang
raspasov
9 days ago
The opposite can also happen (where the whole thing goes white).
bilbo-b-baggins
9 days ago
Metaphor for American politics.
low_tech_punk
8 days ago
maxwell's demon peeking from the dark side
camillomiller
9 days ago
Had the same experience and derived an absolutely unexpected bout of deep existential anxiety from it. Going to touch grass now.
d4rkn0d3z
8 days ago
Tunneling.
gedy
9 days ago
"I am.. Tetsuo."
Hendrikto
9 days ago
> vibe forked a speed control slider
Very on brand, it does not work correctly. I can turn the speed up but not back down again.
francisduvivier
9 days ago
Yes true :D, I kind of just want to blame gpt-5 mini for it and that's one of the bad things about the bad coding, I immediately loose part of the sense of ownership and responsibility. I don't feel like I made it, I just managed it.
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.
rnotaro
9 days ago
This vibed coded implementation is buggy.
If you go to 64.00×, it can't slow back anymore.
francisduvivier
9 days ago
Well that's fixed in the V2 with even more vibe coding:
https://francisduvivier.github.io/eternal-struggle-with-spee...
hk__2
7 days ago
> This vibed coded implementation is buggy.
Isn’t that the main characteristic of vibe-coded code anyway?
ks2048
9 days ago
Yes, going to 32x also won't let you back down to 1x. (16x and lower - yes).
rhubarbtree
9 days ago
Interesting data point on the vibe coding front, as this is very buggy. Doesn’t bode well for releasing an agent on a non-trivial problem!
narrator
9 days ago
It looks like it converges to a normal distribution curve with white being the area under the curve.
loandbehold
9 days ago
Why not other way around?
kelnos
8 days ago
Feature request: show a "scoreboard", that is, with every collision, show the percent of the circle that's white, and percent that's black.
maxlin
9 days ago
Thanks :D I did really want to know what kind of shape it would tend towards over time.
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
pmontra
8 days ago
Of course we want to make a ball faster than the other one and let it win the struggle.
brcmthrowaway
9 days ago
At fast speed I see a trail of the circles. What gives?
patates
9 days ago
something about monitor refresh rate perhaps?