| ▲ | 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 | parent | next [-] |
| Well that's fixed in the V2 with even more vibe coding: https://francisduvivier.github.io/eternal-struggle-with-spee... |
| |
| ▲ | ks2048 9 days ago | parent | next [-] | | Watching it at 100x is cool - you can just watch the border wiggle around (at this speed you may as well not even draw the balls). | |
| ▲ | patates 9 days ago | parent | prev | next [-] | | I think next level would be custom shapes, custom starting areas, more colors, ability to change physics (add gravity?), and user interacting (being able to help a fellow struggling entity -a ball in this case-, when it gets worse). Someone put this into an AI super duper thinking max edition, sprinkle some MCP on top and see what happens lol | | | |
| ▲ | rottc0dd 8 days ago | parent | prev [-] | | Nice work. Still buggy. If you increase the ball size and increase the speed, the whole thing goes black/white in 10 seconds. |
|
|
| ▲ | 9 days ago | parent | prev | next [-] |
| [deleted] |
|
| ▲ | hk__2 7 days ago | parent | prev | next [-] |
| > This vibed coded implementation is buggy. Isn’t that the main characteristic of vibe-coded code anyway? |
|
| ▲ | ks2048 9 days ago | parent | prev [-] |
| Yes, going to 32x also won't let you back down to 1x. (16x and lower - yes). |
