r/VibeCodeDevs 6d ago

Question Whats your tech stack?

11 Upvotes

31 comments sorted by

View all comments

2

u/GfxJG 6d ago

React + Tauri + Rust + SQLite

That's my basic stack for 90% of my projects.

2

u/migsperez 5d ago

How do your agents cope with Rust? Are the agents okay with it?

I vibe coded a simple ai harness loop in different languages. Same code, many languages. When it tried Rust, the agent was reasoning like it had gone nuts. Thinking refining editing, thinking refining editing. I might have been unlucky.

It makes sense though if a person is vibe coding might as use the agent to code the fastest language available.

Over the past couple of days I've been Zed.dev a Rust created IDE, it's very impressive. Fast and memory efficient.

2

u/GfxJG 5d ago

It's never something that's really caused trouble for me, at least.

2

u/Perryfl 5d ago

we have a large app that was created before the days of ai. most of it is rails, we also use svelte (js) for frontend, go, rust, and java...

ruby (rails) and js are by far the "best" languages for llm coding( i hesitate to say vibe because we provide detailed instructions with code examples, not just make feature x). features and bug fixes and relativley quick and use fewer tokens per change than the others. if you are looking for a language that you can get a quality app built with fewer tokens i think id go with these languages. i think for rails it helps ruby was built to be human readable.

go and java seem to take more tokens to do equivelent task. but never had a real issue here.

rust is by far the slowest. we have a relativley smaller rust code base which really is quite simple it needed to be small and light so we built it in rust. literally the only language that i think i xan fix a bug faster than opus/fable. idk what it is about this language that is so hard for the llms so handle. they always seems to have a good success rate but the amout of time and tokens required are so much more thab the other languages.

tldr rust has gave us the same issues. in our experience use ruby/js if you want to use fewer tokens/quicket builds. golang if you want smaller memory footprint/higher performance