[oofbey]

But as we get LLMs to write more of our code, shouldn’t we be moving to languages like Rust, where the compiler is very strict and has lots of checks against subtle bugs? In this sense Python is the worst possible language for vibe coding, because Python allows all sorts of bad code to (mostly sorta) run.

[krzyk]

> In this sense Python is the worst possible language for vibe coding

Javascript would like a word

[tcfhgj]

But JS has TS

[leafario2]

But TS has JS

[krzyk]

But Python is readable, it is the most readable language I've seen.

There is a reason why it is used nowadays as the first language in schools.

[tracker1]

Assuming your editor is using tabs as spaces and preserving whitespace appropriately, for varying definitions of "readable".

[tcfhgj]

I think both are readable

[aaronblohowiak]

Yes! It gives me quite a bit of confidence and makes refactoring easier. Pure rust backend is basically hassle free now with LLMs. Frontend still ts / svelte because of ecosystem and training set.

[hoppp]

Elm is a great front end language for LLMs, its simple and safe and the entire language is in the training set and its not under active development right now so no breaking changes.

[nurettin]

Not under active development as in issues keep piling up and there is nobody to resolve them?

[hoppp]

The language is not actively changing.

It's done, the language is complete.

Issues piling up, Im not sure.. the compiler has only 4 unresolved issues in 2025...

Looking at the github.. they don't seem to be piling up that much.

Sometimes a programming language is well written and its done, no need to actively work on it.

[ra]

Yes. I've switched my vibe-coding to rust, mostly because of the fantastic error messages and compiler feedback

[m3047]

Did you let the LLM horde (it and its agents) compile Rust? Is the LLM allowed to flag problems with Rust? Rinse, lather, repeat...

[sesm]

If you want to eliminate memory issues as a class, just use a language with managed memory.

[rurban]

We should be moving to actually safe languages. Not just safer languages

[oofbey]

What language would you recommend? Or if none qualify what do you think is missing?

[rurban]

There are dozens of memory safe languages, eg. all with a GC. Lisp and .NET comes to mind.

[nacozarina]

type safety was always a guardrail for the human not the machine.

humans aren’t reading code, so no need for it, ai can write everything in ASM & C, keep everything fast and economical.

[JoshTriplett]

> humans aren’t reading code, so no need for it, ai can write everything in ASM & C, keep everything fast and economical.

This is a great plan; I would encourage everyone using AI to follow this strategy. The resulting smoking craters will have many job opportunities for human-written code that works.

[yjftsjthsd-h]

Surely AI also needs guardrails?

[Rexxar]

AI needs heavy fortifications, moats and watchtowers around it.

[justaboutanyone]

People are still going to read the PR regardless of how it was created.

[oofbey]

In some environments this is a hard requirement, and will be hard to break. Places where the code is know to have big impact / blast radius and can’t be wrong.

In other environments (most startups founded in the last six months) no human is ever reading any of the code. It’s kinda terrifying but I think it’s where we are going. And here I would argue having strict compilers is way more important.

[tormeh]

That's fascinating and insane. Rust will help, but I can't see that working well. In my experience LLMs (even Claude) need quite a bit of handholding.

[justaboutanyone]

Perhaps people will move to stricter programming languages try to counter the slop issues

[sunshowers]

?

[nurettin]

Yes, Rust boilerplate is LLM worthy work. It was never meant for humans. The ergonomics component is absent.

Unfortunately, there will be more tokens and context wasted as the LLM struggles with appeasing the compiler.

Example: say a function had two string view args which are bound to a single lifetime because both args at call site had the same scope. Now you have another call site where the args have different scope. Whoops, let me fix that, blah blah.

[simonask]

That’s… not how any of that works.

[nurettin]

That's... suspiciously terse.