> What is a programming language for at this point?... AI could just flip the bits in theory and write machine code. I think the wrong question is being asked.

> What is a programming language for at this point?... AI could just flip the bits in theory and write machine code. I think the wrong question is being asked. Instead of asking "how will a programming language apply," the question should be "how many layers of abstraction are tolerated?" The amount of abstraction is a kind of cost-benefit analysis. In one scenario, it may be more attractive to forego tooling at a more abstract layer, in favor of using under-girding tooling at a less abstract layer. For example, if a software dev is two or more layers deep in plugins/frameworks/libraries and realizes that working with the stdlib would actually take less time. Or, in your scenario, a company using an AI system to write high-level scripts realizes that working with the high-level scripts directly would actually take less time. However in another scenario a software dev may realize that abstraction tooling actually saves time versus working "close to the metal." Or, in your scenario, a company may realize that an AI system actually saves time versus having a human write out boilerplate. > Will a code-writing AI in 2070 be writing assembly... If we're looking into crystal balls for the answer, mine says ~ 50 years is long enough time for drastic changes that don't fit into this conversation at all. But ignoring all that for a minute, the cost-benefit analysis indicates to me that there is plenty of room for bounces and whiplashes. Meaning, a period of lots of AI abstraction, followed by a period of abstraction consolidation/standardization and death.