| ▲ | bita_nidir an hour ago |
| I don't think it'll make sense for an LLM to program directly on the cpu opcode level due to the overhead. But I hope you all realize that the programming language of the future is going to be for LLMs. It'll tightly optimized for LLMs and we'll get nice tools to understand them. They'll probably be great, with loads of fancy tooling. |
|
| ▲ | andai 7 minutes ago | parent | next [-] |
| What overhead? More tokens for same result? I haven't looked into it properly but, it looks like it might actually be the same amount of tokens? (Excepting stdlib boilerplate etc.) |
|
| ▲ | amelius an hour ago | parent | prev | next [-] |
| The programming language of the future will be a purely functional language, where the LLM acts as the compiler using correctness preserving transforms. Any other way of coding will be considered ridiculous (except maybe if you do it for a hobby). Better start learning Haskell, folks. |
| |
| ▲ | WarmWash 43 minutes ago | parent | next [-] | | In its purest form there would be no programming at all, you would just be interacting directly with the AI model. The interface would be like an amorphous digital goo that can instantly shape-shift into any state. | |
| ▲ | bonesss 12 minutes ago | parent | prev | next [-] | | OCaml, F#, or even Rust have functional cores that verify correctness. They’re wire token efficient, too. Sufficiently massaged OCaml/F# approaches straightforward readability in plain English. And, for people who have been doing it for a minute, the other ways of programming do seem a little ridiculous ;) | |
| ▲ | sevenzero an hour ago | parent | prev [-] | | Yea lets just trash all these legacy codebases the world depends on, I'm sure this will work out | | |
| ▲ | raincole 23 minutes ago | parent | next [-] | | You're being sarcastic but it's likely necessary. There will be so many vulnerabilities found in legacy codebases and not enough people who understand them to patch the holes. We'll have to rely on LLM to update them and the once well-understood codebase would be more and more like a vibe-coded one. | |
| ▲ | amelius an hour ago | parent | prev | next [-] | | Legacy codebases are toast. This is where the software world is heading: https://www.youtube.com/watch?v=Bo-vESS4jt0 https://www.youtube.com/watch?v=UCL4K36SHp0 | |
| ▲ | behringer 37 minutes ago | parent | prev | next [-] | | It's like watching a boat pull into port. You can see the boat on the horizon, but people are saying the boat won't be arriving any time soon. The boat's here. Nobody's going to be programming the old fashioned way anymore (except as a hobby or a specialist). You should probably get ready for the boat. | |
| ▲ | bitwize 20 minutes ago | parent | prev [-] | | Claude can rewrite those codebases in Rust in an eyeblink. Let them all burn. |
|
|
|
| ▲ | haolez an hour ago | parent | prev [-] |
| It depends. If you design and train a tokenizer for that, I don't see why it wouldn't work, and I'm not even an "AI psychosis" victim :D |
| |
| ▲ | dezgeg 7 minutes ago | parent [-] | | Emitting a executable binary (eg. ELF) will never make sense over using assembly language. Adding/removing some code to the middle of a large program shifts tons of addresses like jump targets and variables. It makes no sense to have LLM spend tokens on making edits to (potentially) every single call instruction in an existing binary, instead of letting assembler do it. |
|