Thread

Bend – a language that blocks AI mistakes via proof and runs on GPUs

616 points · 327 comments · nicolas-siplis

AlexErrant · 1789678730 · focus · HN ↗
<a href="https://github.com/bendlang/bend" rel="nofollow">https://github.com/bendlang/bend
...did they just squash the repo to 1 commit for v2.0.4? Why? Yall should know that in this age of AI trust is the real currency... and nuking your history is one hell of a way to raise eyebrows.
> Enjoy bug-free, fast vibe-coded apps! Hints: ask it to write laws for whatever should never break, and to parallelize everything you want running fast. Bend is young: if anything goes wrong, ask it to open an issue.
Emphasis mine. I don't want to be snarky but like... come on.
1. LightMachine · 1789680045 · focus · HN ↗
  yes, there's a lot of personal info and AI slop in the commit history.
  is this a problem to you? why
  1. ModernMech · 1789691527 · focus · HN ↗
    To give you a concrete reason why you should care to preserve the exact history and why it’s a matter of trust: in your paper, you reported the pinned SHA head of the benchmarks you ran. When you destroy the history you make it hard for people to duplicate your benchmark results. Why report the SHA if you are going to destroy the history?
    <a href="https://github.com/bendlang/bend/blob/80b6539bc57621633ca68e6e07fbb538d65c1050/bend2/docs/BendRT/main.typ#L524-L529" rel="nofollow">https://github.com/bendlang/bend/blob/80b6539bc57621633ca68e...

Unofficial Hacker News client; not affiliated with Y Combinator.