upvote
Claude is perfectly capable of writing assembly. Here's a working (basic) Prolog interpreter that Claude Fable 5 wrote in WebAssembly in 61 minutes for $16.75 in token costs: https://github.com/emk/fable-wasm-prolog/blob/main/prolog.wa...

WebAssembly is slightly easier than real assembly, but here Fable used WASM GC extensions, which are poorly documented and not yet super common.

Fable didn't even need to debug it; I believe essentially all the assembly worked correctly on the first try.

I have feelings about this, but I'm not pretending it isn't real.

reply
Yeah I had it remake my favorite TI-89 graphing calculator game in Python and it one shotted it perfectly.
reply
The guys with unlimited Fable/Mythos access are for some reason incapable of producing a flawless Claude Code app built entirely in native assemblies.
reply
> They don't have Claude write assembly because there is no training corpus on people making CRUD apps in assembly.

I suspect that despite its translation abilities, this is true, but I'd like to see it do things in languages that are more or less appropriate for tasks to see how much the training corpus matters vs. its ability to translate. Assembly is a bit of an extreme example because you're either writing it as close to C as possible (C is essentially portable assembly) or you're writing complex, unreviewable code that happens to work. And who know if it's been trained on register allocation, or resorts to doing everything on the stack because it works.

reply
What's there to advance to?

Without a revolutionary new platform to build apps on that no one has ever developed for before, there is basically no reason to believe there is any software left that has some business or economic value that hasn't already been written.

reply
This gives "let's close the patent office"
reply
If you think we're "done", you have no imagination.
reply
What are you gonna make? Yet another CRUD app? An API subscription? A game? A mobile app?

We’ve created software for virtually every place we can put software. There’s nothing new.

It’s like bridges. We’ve seen all the ways bridges can be built by now. There’s nothing new left to discover.

reply
> There’s nothing new left to discover.

It's the end of history. What could we possibly discover about a series of technologies that are already nearly 100 years old now?

I've heard people say that various things are "solved" now because of LLMs too -- programming included. This implies we've "solved" thinking. I'm worried about these sentiments.

https://en.wikipedia.org/wiki/End_of_history

reply
When Gutenberg invented the printing press, he could not have predicted the teleprompter. Now that code is easy to generate, it’s plausible that we will use much, much more of it than before.

It’s also a bit ironic to imagine that we’re at the end of new software ideas on a site owned(?) by YC.

reply
it's also plausible that with an ability to generate as much code as we want with little effort, we will quickly discover how much code we actually need, and then plateau at that point.

Personally, I think we've already reached that point.

Even at YC, I have not really seen any startup doing anything interesting where their main value prop is enabled by new proprietary code that does stuff no one else can already do.

reply
Why did we even need bridges in the first place
reply
that you don't see this as inevitable worries me dearly
reply
It's still possible to make CRUD apps in assembly with an AI agent but it would be a research project.
reply
By "research project" you you mean by people who understand assembly? Because then we're back to where we started.
reply
>They don't have Claude write assembly because there is no training corpus on people making CRUD apps in assembly.

I'm disputing this. You can have a training corpus in assembly as big as any other language: just feed the compiled result(in assembly) of the CRUD apps to the LLMs.

reply