The End of Programming

The thread mostly rejected the headline while taking the underlying capability jump seriously. The Bun Zig-to-Rust rewrite impressed many readers as evidence that LLMs can now translate large codebases, exploit strong test harnesses, and grind through enormous volumes of already-understood implementation work. Several commenters argued that this is exactly where a large share of programming lives: reimplementation, adaptation, and translation rather than pristine invention. But the dominant qualification was that the rewrite depended on years of human engineering embedded in its architecture, tests, oracle, and technical objective. Readers argued that turning a vague business need into a correct specification, deciding what tradeoffs matter, and detecting subtle bad decisions remains the work. Current agents can produce a convincing prototype, yet commenters repeatedly distinguished that from maintaining a safe, reliable production system. Limited context, excessive confidence, language-idiomatic mistakes, and buggy AI tooling itself all undercut claims of imminent replacement. The more plausible future, in the thread's view, is a shift from manually typing implementations toward orchestrating models, designing verification environments, and expressing intent precisely. Some see that as democratizing bespoke software; others fear it erodes expertise, narrows junior training paths, and gives executives an excuse to reduce engineering headcount before the technology is dependable.