↓ Skip to main content

·180 words

I think I have to disagree with this post and call it mostly wishful thinking. I haven’t seen that much adoption of vibecoding in Rust. Most of the data points I’m looking at point towards Go being the clear leader here with its low expressiveness, quick compilation and rather basic type system.

It is true thath Typescript isn’t a very good fit. It’s type system is broken despite being too complicated and it brings very little to the table as a programming language on every other front.

The major concerns after the basic code has been taken care of are around organization, factoring and architecture. On those dimensions, you need something with clear defined and loose coupling to allow iterating on parts of the system effectively. Having tussled with crate organization in Rust more than a couple of times, its story there isn’t enormously compelling.

Of course it would be hilarious after being the default language of web3, Rust would graduate into being the language that things are vibe coded in. But again I don’t think this is happening.

https://www.forbes.com/councils/forbestechcouncil/2026/03/03/rust-the-unlikely-engine-of-the-vibe-coding-era/

Alper Cugun
Author
Alper Cugun

Related

·78 words
The goal is not to embed Django inside another system, but to demonstrate that Django ORM can already act as a lightweight, standalone data access layer.

·62 words
We found that using AI assistance led to a statistically significant decrease in mastery.

It’s obvious that international platforms will need to support international writing. The world is a big place and ASCII hasn’t been enough for a while now.