Programming languages — LLMs change constraints landscape
Original excerpt
I think it must be a very interesting time to be in programming languages and formal methods because LLMs change the whole constraints landscape of software completely. Hints of this can already be seen, e.g. in the rising momentum behind porting C to Rust or the growing interest in upgrading legacy code bases in COBOL or etc. In particular, LLMs are especially good at translation compared to de-novo generation because 1) the original code base acts as a kind of highly detailed prompt, and 2) as a reference to write concrete tests with respect to. That said, even Rust is nowhere near optimal for LLMs as a target language. What kind of language is optimal? What concessions (if any) are still…
Frequently asked questions
What is "Programming languages — LLMs change constraints landscape" about?
This article by Andrej Karpathy is part of the Andrej Karpathy reading list on Burn 451, covering ai agents.
Who wrote "Programming languages — LLMs change constraints landscape"?
This piece is part of the Andrej Karpathy vault on Burn 451, covering ai agents. The original author is attributed at the source link.
How can I read more content from Andrej Karpathy?
The complete Andrej Karpathy reading list is available at burn451.cloud/vault/karpathy. Each article includes an AI-generated summary so you can decide what to read in seconds. Connect the Burn 451 MCP server to Claude or Cursor to query all Andrej Karpathy articles as live AI context.
Can I use "Programming languages — LLMs change constraints landscape" with Claude or Cursor?
Yes. Install the burn-mcp-server npm package and connect it to Claude Desktop, Claude Code, or Cursor. Once connected, your AI can search and reference this article and the full Andrej Karpathy vault in real time — no manual copy-paste required.
37 more articles in this vault.
Import the full Andrej Karpathy vault to Burn 451 and build your own knowledge base.
Content attributed to the original author. Burn 451 curates publicly available writing as a reading index. For removal requests, contact @hawking520.