Gorilla Gauntlet (Based on the Gorilla vs 100 men meme)
Check it out here: https://gorillagauntlet.replit.app/ (didn't use replit, just hosting it here)
I have to say I was a bit... whelmed.
Trying to play around with vibe-coding and I thought I would take a detour and try my hand at creating a game. I actually started off in grok, first discussing the concept for the game, and asking it to help me come up with more feature ideas and eventually to help me create a well-organized prompt that would help me to one-shot a viral game. Grok was very confident it could implement all of the wonderful features we came up with, but in the end it gave me an html file full of runtime exceptions that it couldn't successfully debug for me.
So I took the prompt to GPT5 - which performed much better! Initially it tried to have it build all of the fancy feature Grok came up with but it also broke so I asked it to pare down the feature set. Once we got a working prototype I was able to start vibe-adding game features.
The good:
- Pretty decent "MVP" built within an hour. Haven't touched code in 10+ years but imagine this would have taken me days+ to get something similar up and running.
- I literally didn't have to touch any code at all. When it broke I just copy-pasted and described the errors and GPT5 diagnosed and fixed the bugs.
- It did a pretty decent job implementing new features, all "programmed" in english via prompting.
The bad:
- The game kind of sucks lol. I was expecting to one-shot a really cool viral 3d game out of the box with all sorts of cool rag-doll gorilla-tossing-human physics. Instead I got a bunch of bumbling blocks/cylinders that took quite a bit of prompt work (longer than I'd like to admit) to refine to somewhat presentable appearance. I guess this is more a limitation of Three.js as it got my underpowered laptop burning quite hot.
- Token output is really slow. File grew to about ~1200 lines and it got very slow spitting out tokens for each small update.
- "No you screwed something else up, fix this" doom loop got really frustrating. You really need to have some reading material available during downtime. I did everything via ChatGPT interface, I assume if I had tried this with cursor I could have manually fixed some of these bugs much more quickly.
I'm tempted to be a troll and tweet out that this game was one-shotted by Grok and see if it gets retweeted by Elon since he seems to be actively amplifying any and all grok ass-kissers in an attempt to throw shade at openai.