The next few years are going to be fun.
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.
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.
Now, developer productivity is becoming less important as developers are factored out entirely.
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.
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.
Already when coding on cloud environments like Workato and Boomi there is no code output to look at.
I’ll probably switch to Rust for the automated stages. I read C++ more easily, but maybe I don’t need to much longer.
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.)
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.
It's the lack of clear abstraction boundaries that causes decreased developer productivity.
A code generator will not save you from Conway's law.
UNIX. Seriously. Look at what it could do with 1970s era hardware, that was unmatched even when DOS came out in the early 80s.
During the 1970's, VAX/VMS and Xerox PARC workstation OSes, ML, CLU, were more inspiring for 1970's hardware capabilities.
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...