1–10 of 99 posts
I hope you can humour me and not challenge the assumptions baked into the question. That's a separate, if interesting, exercise.
It would need interop with a large subset of existing Python/C libs to ensure adoption.
Having a lot of experience with programming in C++. C# and JavaScript, I have found that many 'creepy' bugs are related to the confusion arising from assigning an object to some member, where a copy is intended, or the otherway around, that a copy is made where a reference is intended. I have not yet come across a language where this is solved and have started working on such a language myself: https://github.com/FransFaase/DataLang
The next leap was LISP Machines and Smalltalk Single Image Systems, where the developer was given a unified vertically-integrated environment further increasing their productivity. Some even called it a "human–computer symbiosis". But unfortunately this approach has not become mainstream, though I worked with some proprietary database systems based on a Single Image System.
Next we had an era of "Application Generators" or "Fourth Generation Programming Languages". They made application developer's job easier and were closer to modern LowCode/NoCode tools.
Modern SDLC is a chaotic collection of different methodologies, practices, techniques, patterns, and tools (the PLs are just one of these tools). They were created in evolutionary way by optimizing for local maximas, and they might missed the global one.
To summarize, IMO what we need is a higher level application development environment supporting all stages of the modern SDLC, not just a new programming language which will solve only the coding part.
Most programming being done is either DB backed CRUD APIs & UIs.
For the first part, having to write a REST API is mostly repetititve, not same but similar logic.
Some well designed ORMs & automatic wrapper generators get you quite far (compared to hand writing SQL), but the mismatch is still there.
The best backend language will natively work with database. I haven't worked with many technologies in this, but spring data jpa looks like a good initial step to look at.
Second one is UI. Reactivity is the norm but languages are still mostly procedural. Look at all the state management confusion in eg. Flutter.
Svelte is a quite big step here. I think UI language of future should have reactivity built in.
Programming Languages initially were called "Higher-Level Programming Languages" to contrast them with the "Low Level Machine Languages" / Assembly. Back then there was an understanding that you can increase productivity by using higher-level languages over low-level languages. The next leap was LISP Machines and Smalltalk Single Image Systems, where the developer was given a unified vertically-integrated environment…