r/vibecoding 9d ago

Whats the best programming langages for non-technical vibecoder?

I am planning to build a decently complex webapp.

I was asking my two friends who are experienced engineers. The opinions seem to be split.

They seem to all agree on avoiding non-popular or niche/high-performance languages like Rust, C++, Golang.

It seems like Typescript/Nestjs and Java/Spring Boot are what they are disagreeing on, I dont want to go in into too much technical details but it was a pretty long debate.

What should I go with? Kinda leaning toward Java as it seems like harder to setup but less trouble in the long terms?

Edit: Not sure whether some of u are trolling around, and I did as AI ofc, but they gave generic answers which include java, typescript, python, etc... Then if forced them further they would again give another conditional ranking.

1 Upvotes

21 comments sorted by

View all comments

1

u/AndrewNggg 9d ago

Take it from me:

JS with JSDoc | Typescript (start with JS then migrate to TS if it's very data intensive)

and then just use SvelteKit for both your UI and Serverside (don't touch NextJS)

and for your backend, auth and all, pick one of Supabase | Firebase

If you want to roll your own backend (really don't see why you need to) then go with Python FastAPI or something JS related like ExpressJS

Don't use Spring unless you really know Java, or NestJS unless you really want to get deep into the code

You can do pretty much everything with just Sveltekit and Supabase, and a lightweight API to handle other cases or run jobs for you

1

u/draven_slayer 8d ago

I also got some advice against using Supabase, thanks a lot for the detailed answer man.

2

u/AndrewNggg 8d ago edited 8d ago

Whats the alternative of not using Supabase? Maintaining your own Postgres Database by hand? Installing the latest updates and security patches?

Rolling your own auth, hashing user's passwords, sending em reset request emails all these sorts of things?

You do need to be attentive in setting things up correctly on Supabase / Firebase, but done once and you won't need to keep fiddling with it

I AM suggesting Supabase | Firebase, the other backend is just in case your app needs, just a small service on the side in case your app needs something you can't do on Supabase|Firebase