AI thinks in Python and talks in JavaScript!
AI thinks in Python and talks in JavaScript!
I didn’t get this from a survey. I got it from watching the tools.
Ask Antigravity, running Gemini Flash, to build something — don’t name a language, don’t name a framework. It reaches for Python and JavaScript. Ask Muse Code, running Spark models, the same way. Same answer. Nobody told them to. That’s the default. And the default is the evidence.
Python is the default for thinking because there is nothing in the way. No compile load. When you’re developing and you don’t yet know how the application will pan out — what it does, what it looks like — a scripting language is the cheapest place to think. You change your mind in seconds instead of minutes. You reshape the thing while you’re still discovering what it is. The thinking stays fluid until the shape settles, and only then do you harden it.
So the claim, stated plainly: AI thinks in Python and talks in JavaScript. I checked it against the numbers. It holds — with one clean split.
AI thinks in Python — holds
Python is the number one language for AI work: 39.0% of developers use it with AI tools (Stack Overflow Developer Survey 2026), ahead of JavaScript itself at 38.4%.
It leads AI-tagged repositories on GitHub — 582,196 of them, up 50.7% year over year, roughly half of all new AI projects (GitHub Octoverse 2025).
And the evaluation regime — the tests that decide which model is “smart” — is Python-only. HumanEval is 164 Python problems. SWE-bench is 2,294 real issues from Python repos. A review of 24 major coding benchmarks found 95.8% of them focus on Python.
The models themselves agree. When the language is unspecified, more than 90% of the code they generate is Python — and even on problems where Python is clearly the wrong choice, they still pick it about 35% of the time. OpenAI’s Code Interpreter is literally called “the python tool.”
AI talks in JavaScript — mostly holds
JavaScript runs on about 99% of websites. It is the most-used language overall at 62.0% of developers, for the 12th straight year. TypeScript is now the number one language on GitHub by contributors, and npm is the largest software registry in the world at over 3.5 million packages.
The flagship AI products speak it. ChatGPT’s web app is React, Next.js and TypeScript. VS Code — the coding agent’s home, used by three quarters of developers — is TypeScript on Electron.
Where it breaks — and the article carries these, not hides them
The compute is C++ and CUDA. PyTorch and TensorFlow do their tensor math there; Python orchestrates, the FLOPs happen elsewhere. The dominant local inference engine, llama.cpp, is pure C/C++.
And JavaScript breaks off the browser. Native mobile apps are Swift and Kotlin. Voice is screenless — there is no browser in the loop at all. And the most-used coding agent of 2026, Claude Code at 65.5%, is terminal-first.
Read literally, “thinks in Python” is false twice over: models reason in tokens, not in a programming language, and the actual computation is C++/CUDA. But as a description of the engineering stack’s division of labour, the sentence is strikingly accurate.
Python is where AI is authored. JavaScript is where users meet it. The two halves don’t compete — they divide the labour. And the models told us first: leave the language blank, and they think in Python and talk in JavaScript.
Sources
- Stack Overflow Developer Survey 2026 — https://stackoverflow.co/company/press/archive/stack-overflow-annual-developer-survey-ai-trust-conditional/
- GitHub Octoverse 2025 — https://github.blog/news-insights/octoverse/octoverse-a-new-developer-joins-github-every-second-as-ai-leads-typescript-to-1/
- OpenAI Code Interpreter docs — https://developers.openai.com/api/docs/guides/tools-code-interpreter
- W3Techs, Web Technologies of the Year 2025 — https://w3techs.com/blog/entry/web_technologies_of_the_year_2025
- LLM Python preference — https://www.zansara.dev/posts/2026-10-19-is-python-the-favorite-language-of-llms/
- Coding-benchmark Python dominance — https://javapro.io/2026/10/15/llms-for-jvm-code-in-2026-which-models-to-trust-which-benchmarks-to-believe/
Write a comment