▲ | timuckun 3 hours ago | |||||||||||||
It's been my experience that strongly opinionated frameworks are better for vibe coding regardless of the type system. For example if you are using rails vibe coding is great because there is an MCP, there are published prompts, and there is basically only one way to do things in rails. You know how files are to be named, where they go, what format they should take etc. Try the same thing in go and you end up with a very different result despite the fact that go has stronger typing. Both Claude and Gemini have struggled with one shotting simple apps in go but succeed with rails. | ||||||||||||||
▲ | topato 3 hours ago | parent | next [-] | |||||||||||||
This is pretty anecdotal, but it feels like most of the published rails source code you find online (and by extension, an LLM has found) is from large, stable, and well-documented code. | ||||||||||||||
| ||||||||||||||
▲ | delifue 3 hours ago | parent | prev | next [-] | |||||||||||||
In my experience Gemini can one-shot go apps. Determining it requires sound eval instead of anecdotes. | ||||||||||||||
| ||||||||||||||
▲ | EGreg 3 hours ago | parent | prev [-] | |||||||||||||
Basically it's like this: the more constraints you have, the more freedom you have to "vibe" code and if someone actually built AI for writing tests, catching bugs and iterating 24/7 then you'd have something even cooler |