I have also been using LLMs (mostly claude code) to develop a game with Rust and Bevy, and it seems to work very well. The strictness of rust seems to really help them get the code right, and the ECS architecture seems to make it easy for them to reason about how things work (because they only need to hold a few systems and components in context at a time). makes me wonder if ECS will ever catch on outside the gaming…
Games and other specific applications call for such unidirectional data flow with such massive amounts of "independent" entities. It isn't that it'll catch on or not outside the gaming industry, it is more of a unique solution to a typical gaming problem. So their are apps that do use similar or ECSs architecture under the hood, it is just more problem related not a solve everything solution.
Show HN: A self-running space economy SIM in Rust and Bevy
31–34 of 34 posts
Re: Show HN: A self-running space economy SIM in Rust and Bevy
#32It’s fun to see projects like this that seem largely unlocked by LLM assistance, and probably wouldn’t even get started if it weren’t for them. I know the hype cycle for LLMs seems to have hit its peak already, but I am fully convinced we are still in the early days of what we’ll be doing with them in software development. The only problem I see with projects like this is that there could be so many of them. Personal…
Re: Show HN: A self-running space economy SIM in Rust and Bevy
#33Earlier quoted context omitted.
I'm a Rust dev, but I've been worried Claude might not be able to emit Bevy (or Fyrox) sufficiently well. I keep seeing Mr.Doob post amazing stuff in Threejs and the vibe coding scene blowing up with all kinds of generative work, and I feel really drawn to it. Do you feel like Claude gets Bevy well enough? I know it kicks ass at Rust, but Bevy is relatively niche still. Do you feel like Bevy is pretty performant?
yeah it does fine with bevy. It struggles a bit to structure the components in the best way, so that still requires some human oversight if you want it to be good. It helps a lot to emphasize that you want "idiomatic" bevy code, and ofc it also helps a lot to spend a lot of tokens on design and review (e.g. "is this the most elegant way to structure these systems/components?"). There's also this feature called Bevy R…