News for hackers. Stuff that matters.
Re:Things That Turbo Pascal Is Smaller Than (2011) by hawkice on Sunday November 15, 2026 @09:14AM (#50507082)
Given development speed is way up, I'd be interested to see what a from-basic-principles simple and efficient OS and programming system might look like.
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.

Re:Things That Turbo Pascal Is Smaller Than (2011) by Isamu on Sunday November 15, 2026 @10:15AM (#50507497)
>Fundamentally, many inefficiencies were justified for developer productivity, and I'm not sure that makes sense anymore

Having lived through this period, I would disagree, quite the opposite we tended to develop in C and assembly specifically for runtime efficiency because we had to.

For developer productivity you could opt for Lisp or SmallTalk or some such, which ran much slower until high quality compilers for these became available, and even then your target machine might only have a C compiler.

Re:Things That Turbo Pascal Is Smaller Than (2011) by za_creature on Sunday November 15, 2026 @10:28AM (#50507641)
Specifically, turbo pascal was entirely written in assembly according to wikipedia (I recalled only 50% but maybe that was some other pascal dialect)
Re:Things That Turbo Pascal Is Smaller Than (2011) by SoftTalker on Sunday November 15, 2026 @11:32AM (#50508224)
I read GP's comment differently, that we ended up where we are today (bloated languages, IDEs and runtimes) due to chasing developer productivity at all costs.

Now, developer productivity is becoming less important as developers are factored out entirely.

Re:Things That Turbo Pascal Is Smaller Than (2011) by hawkice on Sunday November 15, 2026 @12:02PM (#50508511)
This was my intended meaning -- the clearest advocacy of this was from DHH about Ruby on Rails, although he's changed his mind about big questions lately and suspect he no longer endorses that set of trade-offs (I don't either, _sort of_ -- I think developer productivity means having simple ways to enable large-scale testing and oversight while minimizing context switching costs, although I think we are all figuring out what that means in practice).
Re:Things That Turbo Pascal Is Smaller Than (2011) by LeFantome on Sunday November 15, 2026 @07:30PM (#50512505)
We will end up with something that is easier for AI to write, efficient to execute, and possible for people to audit.

Rust is becoming popular as LLM output. The resulting code is very efficient. The compiler helps keep the LLM on track and holds it to a minimum level of quality. Humans can read it if they want to. But it is not great to read.

Python is also a popular target. Easy to audit. LOTS of training data. The “one way to do it” philosophy of Python helps. But the resulting code is not very efficient.

I think we will end up with a new language that balances all these things better.

Re:Things That Turbo Pascal Is Smaller Than (2011) by drfloyd51 on Sunday November 15, 2026 @08:27PM (#50512924)
I don’t think we will. Well maybe for a bit. But I think eventually LLMs will produce a kind of byte-code or IL.

Maybe it will have human words inside of it to explain the parts.

Most of the way we organize code is to support our brains. Code reuse via classes and functions. Extensible patterns. Classes.

AI doesn’t need all that stuff. Consider, AI needs what assembly needs. And assembly doesn’t have any of those conveniences.

At some point AI will stop writing code for us to pretend we own and start writing it for itself. I am curious to see what conventions arise to support a programmer whose brain has infinite storage capacity and can figure out what existing code does without having to remember or read documentation.

Re:Things That Turbo Pascal Is Smaller Than (2011) by jiaaro on Sunday November 15, 2026 @10:12PM (#50513591)
Not all of that abstraction is solely to help us understand. Much of it is to make iterating on the code over time simpler and more reliable: avoiding unintended side effects, for example.
Re:Things That Turbo Pascal Is Smaller Than (2011) by pjmlp on Monday November 16, 2026 @02:43AM (#50515086)
Unit tests for AI.
Re:Things That Turbo Pascal Is Smaller Than (2011) by pjmlp on Monday November 16, 2026 @02:43AM (#50515084)
That is my view as well.

Already when coding on cloud environments like Workato and Boomi there is no code output to look at.

Re:Things That Turbo Pascal Is Smaller Than (2011) by robotresearcher on Sunday November 15, 2026 @09:52PM (#50513439)
I’ve done some work using Python for design iteration with me in the loop, followed by a hands-free reimplementation in C++ with byte-identical testing, then into another fully automated perf loop.

I’ll probably switch to Rust for the automated stages. I read C++ more easily, but maybe I don’t need to much longer.

Re:Things That Turbo Pascal Is Smaller Than (2011) by majormajor on Sunday November 15, 2026 @11:25PM (#50514025)
Rust isn't my personal favorite for having agents drive development because the compile time penalties add up fast unless you stay on the agents with prompts/AGENTS.md/etc directives to really keep it from re-running full compile/test suites every iteration.

It can be the difference in a loop that an agent can crank on in Go for 15-30min while I get a coffee vs taking multiple hours in Rust, sometimes.

Anything agent-focused language/ecosystem wise needs to focus on small-blast-radius/fast-iteration.

(Unless/until there's a generational leap in the raw coding ability of these tools to be able to get it "right" (for larger-and-larger definitions of "right") the first time.)

Re:Things That Turbo Pascal Is Smaller Than (2011) by robotresearcher on Sunday November 15, 2026 @09:45PM (#50513405)
It’s a polyglot stack to the extreme these days. The dev lives in Claude Code, running TypeScript and JavaScript, and calling into servers likely written in Go and Rust, which call into Python running CUDA.

Dev is likely generating JavaScript, C++, Python, SQL for corporate work, or Kotlin and Swift for mobile.

It’s much more diverse than back in the 90s. Kinda fun.

Re:Things That Turbo Pascal Is Smaller Than (2011) by za_creature on Sunday November 15, 2026 @10:25AM (#50507608)
I think you have that backwards.

It's the lack of clear abstraction boundaries that causes decreased developer productivity.

A code generator will not save you from Conway's law.

Re:Things That Turbo Pascal Is Smaller Than (2011) by hedgehog on Sunday November 15, 2026 @01:26PM (#50509336)
v8 is pretty complicated, and anything that depends on LLVM is going to be huge, so I think I would start smaller. You could try building around something like NuttX or an L4 + tcc or cproc and see what it takes to get to self-hosting as well as ability to do some job you care about. To me the bigger question is that last bit, you can shrink the platform code quite a lot relative to a typical Linux but what's the situation where that's a good trade vs say cross-compiling from a full C++ or Rust toolchain?
Re:Things That Turbo Pascal Is Smaller Than (2011) by userbinator on Sunday November 15, 2026 @11:39PM (#50514106)
I'd be interested to see what a from-basic-principles simple and efficient OS and programming system might look like.

UNIX. Seriously. Look at what it could do with 1970s era hardware, that was unmatched even when DOS came out in the early 80s.

Re:Things That Turbo Pascal Is Smaller Than (2011) by pjmlp on Monday November 16, 2026 @02:46AM (#50515098)
I rather look to the 1960's hardware with Burroughs, Multics and Lisp.

During the 1970's, VAX/VMS and Xerox PARC workstation OSes, ML, CLU, were more inspiring for 1970's hardware capabilities.

Re:Things That Turbo Pascal Is Smaller Than (2011) by mike_hearn on Monday November 16, 2026 @04:27AM (#50515667)
Ahhhhh this is a common misconception and it's dangerous. V8 is not a battle tested sandboxed execution environment, not unless by battle tested you mean battle wasted. V8 is full of sandbox escape vulnerabilities practically "by design", always has been, probably always will be - and the Chrome engineers knew this from the start which is why from day one they invested so heavily in kernel-level sandboxing.

But! Very important! The kernel sandbox is NOT A PART OF V8. It's not even reusable or modular, it's a hard coded part of Chrome's startup sequence and tuned for Chrome's exact needs. If you embed V8 via its API you don't get it.

I've seen this misconception several times now including in quite serious places, where people talk as if V8 on its own has a robust sandbox. It doesn't! This will blow up in people's faces eventually.

If you want a JS engine that's secure by design then the only one I know is GraalJS, as it's written in a memory safe language and uses partial evaluation to create its compiler so you can't get interpreter/JIT mismatches. It also has a proper sandboxing API and can transparently run code out of process. They're adding Landlock support to that now so it actually will get a built in kernel sandbox on Linux.

This issue vexes me enough that I wrote a whole article about it:

https://medium.com/graalvm/writing-truly-memory-safe-jit-com...