It is beginning to look like the future is treating Rust as an optimization pass. Write your program in a higher-level language like Typescript, Go, Python, etc. and then have LLMs compile that to Rust.
Theoretically the LLMs could go straight to machine code. No need for any intermediate language. However, the HN stories have made it clear that LLMs are not great at going directly to machine code or Rust. Rust is, time and time again, is being used used as an optimization intermediary. If LLMs were better to target it directly they wouldn't be reading report after report about translating to it from another language.
Yesterday I asked Claude to make a RISCV emulator like qemu in x86 assembler. It runs about 5x slower than qemu. That's a pure interpreter vs one of the best JITs. Qemu can run many more instructions though.
Given the rate of progress, it's hard to argue why this couldn't be a reality.
If in the future Taalas-type chips with baked in frontier models are commonplace, this should be quite different price-wise from what we have now.
It's a bit dizzying to imagine that LLMs might even be able operate at speeds of chatjimmy.ai, but we already have working tech that does exactly this (albeit with less intelligence/capabilities).
Not really, the future are natural languages, with some markdown files for formal specification, yaml or whatever, and then Assembly gets generated directly.
3 GLs are going to slowly fade out as LLM tooling improves, and coding looks increasingly as envisioned by 4 GLs advocates.
Sounds awful, natural language sucks for describing complex problems and relationships. That's why people have historically reached for diagrams and pseudo code.