News for hackers. Stuff that matters.
Re:Things That Turbo Pascal Is Smaller Than (2011) by pocketarc on Sunday November 15, 2026 @10:10AM (#50507458)
This is the thing - when the cost of iterating and grinding compiler warnings drops to virtually 0, what new paradigms might we invent to exploit that? Rust gives us an inkling of an idea of what might be possible, but that still predates LLMs and thus still makes concession for human ergonomics. What are structures, guardrails, and patterns, that our OSs, frameworks, and toolchains can put in place, which would result in whole classes of problems going away completely, at the expense of massively increased (but mechanical, and easily automatable with a prompt) developer effort?

The next few years are going to be fun.

Re:Things That Turbo Pascal Is Smaller Than (2011) by tomaskafka on Sunday November 15, 2026 @11:50AM (#50508392)
This would be fine grained type systems where invalid states are inexpressible.
Re:Things That Turbo Pascal Is Smaller Than (2011) by StilesCrisis on Sunday November 15, 2026 @01:07PM (#50509144)
Both humans and LLMs struggle with slow iteration times.
Re:Things That Turbo Pascal Is Smaller Than (2011) by drfloyd51 on Sunday November 15, 2026 @08:34PM (#50512964)
I imagine a kind of language which is just a bunch of declarative statements about conditions and what should happen. Basically BDD. Maybe we will just write the “unit tests” in human and AI writes more comprehensive specification to fill in the blank and for us to modify. And then AI makes code that satisfies the spec.

I don’t believe that source code is a spec. Source code has real time manipulation a kind of temporal dependency. Specs are declarative.

The difference is a spec would say: adding two and three should equal five. Code says you have a variable give it the value two. Now add three to it. Return that value. Maybe a unit test to assert it returned 5.