Is Haskell 'unsafe' too? A debate on types vs verification in the LLM era
satnam6502 · x · 2026-11-22
ChrSzegedy argues Haskell can be more critically unsafe than C (easy to create, hard to find memory bugs) and predicts programming's future is full-blown verification, making language choice irrelevant. satnam6502 corrects that this is a space leak — a performance issue, not a functional bug — noting standard Haskell is memory-safe absent unsafePerformIO, while agreeing that LLMs now code well in just about any language.
More from coding & agent
- Chinese devs vent: app store rejections and copycats are just the norm — tinyfool · 2026-11-22
- Lessons from building a desktop AI agent that sees your screen and drives the mouse — SpeechAggravating453 · 2026-11-22
- MCP server checks if a pay-per-call x402 API is worth paying, from 24,766 real paid calls — biryaniAssasin · 2026-11-22
- Walmart and Muse to launch first agent-to-agent agentic commerce integration over MCP — AccBalanced · 2026-11-22
- scientific-toolkit: one MCP server fronting nine repos that refuses to fabricate results — Emergency-Tutor-7 · 2026-11-22
- Zero-degradation Strata tuning: fixing layer_split lifts decode ~10-15% and halves CPU expert misses — PathfinderTactician · 2026-11-22