Why AI-Built Apps Keep Landing in JavaScript
So many AI-built apps end up in JavaScript. What that says about training data and feedback loops, and whether vibe coding will stay tied to the web stack.
This article is published in English.
Vibe coding is the practice of describing what you want to an AI tool and letting it produce most of the code. You steer in plain language, skim the result and keep nudging until it works. Depending on who you ask, that's either the future of programming or a fad.
A joke has been circulating among developers that vibe coding is secretly just JavaScript with extra steps. It's a joke, but it has a grain of truth.
Look at what people actually build with these tools: landing pages, dashboards, small SaaS products, browser extensions, prototypes and weekend startups. Most of that work runs on React, Next.js, Node.js and their relatives, so the output is overwhelmingly JavaScript or TypeScript.
There are good reasons for the overlap. Models write JavaScript well because they've seen so much of it. Public repositories, tutorials, forum answers and documentation about the language are everywhere, and the training data reflects that. The ecosystem's conventions are also fairly uniform, so a model that has seen a thousand Next.js projects can guess what the thousand-and-first should look like.
The web also gives the best feedback loop. Ask for a landing page and a minute later it's open in a browser tab. Ask for a dashboard, an API or a small app, and you can click through it right away. If a button is misplaced you say so, and the page updates. That immediacy is a big part of why vibe coding feels like magic, and why demos usually involve a website.
None of this confines the practice to one language. People already use AI assistants with Python, Java, Go, Rust, C++ and plenty more. Backend services, data scripts, command-line tools and systems code can all be generated and edited this way. They're just harder to show off. Nobody gets a satisfying screenshot from a database migration or a build script, so those stories travel less.
So the more interesting question isn't whether vibe coding belongs to JavaScript. It's whether programming itself is shifting from writing code to describing the software you want, with a human reviewing, correcting and deciding what ships. If so, the language underneath matters less over time, and the skills that count are clear specification, good judgment about what the machine produced and the ability to notice when it's wrong.
We're likely still near the start of that shift.