Bend programming language
Ranked 50 of 163 programming languages by recommenders
Recommended as a language built for proofs and GPUs, where AI-written code gets checked by formal laws; critics say proof checking can't confirm the laws match intent.
Recommended as a language built for proofs and GPUs, where AI-written code gets checked by formal laws; critics say proof checking can't confirm the laws match intent.
74 people gave an opinion
- recommend it
- 36
- criticize it
- 38
- approval share
- 49%
Recommended in 5 of 13 months
- November 2025: recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 36 people recommend itNeeds 10 or more, met.
- 0.9 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 5 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Proofs suit AI-written code
“I argue this is the right tradeoff, because AI write proofs, and AI time is cheap, while bugs take human time, which is expensive.”
Comment from 17 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” “I like the idea of a language intended from the start to be proved and it seems very compelling given coding agents.”
Comment from 17 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” “Since AI is going to be here anyway, why not make it safer and more useful?”
Comment from 18 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” Fast checking and GPU execution
“Having a checker that is just fast by construction, regardless of caching, was a top design priority”
Comment from 18 Sep 2026 in “Bend 2 and the Vibe-Coding Trap” “Seems like a big limitations. But I guess that's what lets it run without GC, on GPUs, etc.”
Comment from 18 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” “Programs that can be easily expressed in Bend will benefit greatly from HVM.”
Comment from 25 Apr 2026 in “Lambda Calculus Benchmark for AI” Interesting design and syntax
“Pivots are cool but why reuse the name and cause confusion?”
Comment from 18 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” “Glad to see a new release of Bend, fascinating cutting-edge stuff.”
Comment from 18 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” “From what I can tell it looks nice. I like the syntax.”
Comment from 17 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” - Comment from 18 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs”
Recent releases keep coming
“Glad to see a new release of Bend, fascinating cutting-edge stuff.”
Comment from 18 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” “A complete implementation have been released”
Comment from 18 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” “Cool to see Bend 2.0 release!”
Comment from 17 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs”
What people warn about
Each mark is one comment
Proofs may miss intended behavior
“it's obvious that the translation from business requirement to proof target still requires coding and can contain bugs”
Comment from 18 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” “Bend would make Dijkstra happy even when proof checking can't verify if the laws are what was actually meant.”
Comment from 18 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” “I'm not sure what its proving other than there will be cases that proofs can't help you with.”
Comment from 18 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” Overstated claims and marketing
“it editorializes and oversells. It presents the claims of the work as an all encompassing solution”
Comment from 17 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” “there's no such thing as a computer programming method or discipline that "blocks AI mistakes via proof."”
Comment from 18 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” “The whole thing smells like somebody trying to pull an LLM-fueled Sokal Hoax on the programming world.”
Comment from 18 Sep 2026 in “Bend 2 and the Vibe-Coding Trap” Vibe-coded, AI-generated code concerns
“it is not a pretty file and it has a lot of gambiarra and AI slop for now”
Comment from 17 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” “This is a vibecoded project, not a resource for learning modeling for formal verification.”
Comment from 31 Oct 2026 in “AI, Lean, and the Future of Formal Verification, with Lean Creator Leo de Moura” “bend is just one example of people having ai build things for them they don't understand”
Comment from 18 Sep 2026 in “Bend 2 and the Vibe-Coding Trap” Trust issues with repo history
“has no auditable history, reproducible builds, artifacts/releases, force pushes and breaks literally EVERY fork/PR”
Comment from 18 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” “That's a destruction of trust, which is kinda important if you want people to build on your language.”
Comment from 17 Sep 2026 in “Bend – a language that blocks AI mistakes via proof and runs on GPUs” “They just recycled the Bend1 repo for Bend2 even though it's a completely different language.”
Comment from 18 Sep 2026 in “Bend 2 and the Vibe-Coding Trap”
Other programming languages people recommend
The four most recommended other programming languages, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
See all 163 programming languages, rankedWhat people said
40 of the 99 comments that mention it, newest first. Each links to the original comment.
“This is a vibecoded project, not a resource for learning modeling for formal verification.”
“the laws are formally verified, as in Lean or Rocq (but much faster)”
“I hope people will give it a second look, and not just stop at this post which is a gross misrepresentation of Victor Taelin's work.”
“bend is just one example of people having ai build things for them they don't understand”
“isn't some vibe-coded fantasy, and the author has been working on this stuff for a loooong time”
“it had only 24-bit integers, a 2 GB memory cap, and other limitations that made it unpractical”
“The whole thing smells like somebody trying to pull an LLM-fueled Sokal Hoax on the programming world.”
“it's obvious that the translation from business requirement to proof target still requires coding and can contain bugs”
“this whole bend thing might be an exact fit for the problem space”
“It would work much better if a) tokens were free and b) computation, therefore retries, didn't take any time at all.”
“Having a checker that is just fast by construction, regardless of caching, was a top design priority”
“They just recycled the Bend1 repo for Bend2 even though it's a completely different language.”
“Every single part of Bend is an intentional choice I made after considering every alternative.”
“despite the presentation of their work, which has some obvious flaws”
“there's no such thing as a computer programming method or discipline that "blocks AI mistakes via proof."”
“Cool project! This is really interesting”
“Seems like a big limitations. But I guess that's what lets it run without GC, on GPUs, etc.”
“I'm only reading these comments because i liked the interaction combinator Bend language.”
“Pivots are cool but why reuse the name and cause confusion?”
“has no auditable history, reproducible builds, artifacts/releases, force pushes and breaks literally EVERY fork/PR”
“Thank you for adding a 5-line AGENTS.md. Other projects force you to install skills or MCP even when they're just doing the same thing.”
“Glad to see a new release of Bend, fascinating cutting-edge stuff.”
“I'm not sure what its proving other than there will be cases that proofs can't help you with.”
“A complete implementation have been released”
“Bend would make Dijkstra happy even when proof checking can't verify if the laws are what was actually meant.”
“Since AI is going to be here anyway, why not make it safer and more useful?”
“it editorializes and oversells. It presents the claims of the work as an all encompassing solution”
“You're basically shrinking the state space of what is considered a "correct" program per your spec.”
“a variation of programming language like this is bound to win”
“LAWS.bend makes you need to read astronomically less code”
“It basically succeeded but Claude (Opus 5) did have some complaints”
“That's a destruction of trust, which is kinda important if you want people to build on your language.”
“From what I can tell it looks nice. I like the syntax.”
“I like the idea of a language intended from the start to be proved and it seems very compelling given coding agents.”
“they just modify the law itself to fit the new feature they are working on, which defeats the point”
“I argue this is the right tradeoff, because AI write proofs, and AI time is cheap, while bugs take human time, which is expensive.”
“it is not a pretty file and it has a lot of gambiarra and AI slop for now”
“Cool to see Bend 2.0 release!”
“I was annoyed with ads and limitations so I built one for myself.”
“Programs that can be easily expressed in Bend will benefit greatly from HVM.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.