Respectfully I think you're missing the point; the future is new kinds of programming paradigms emerging. Consider punch cards evolving into the Burroughs 5XXX evolving into compilers evolving into, "live systems" (Smalltalk, Erlang's BEAM) which laterally gives rise to REPL-style interaction which makes the previous "write a tome and let the computer read it and then let you know what it thinks" seems superfluous and antiquated compared to, "the computer is listening and will respond back instantaneously when it is talked to." It's worthwhile to think in those kinds of terms-- we can with historical precedent consider that whatever supersedes current human-computer interaction will probably be along similar lines. I think so far we've gotten to a kind of responsive Cartesian, List-evaluating (wink, wink) object which can respond to our commands and that's where modern L337bro from California coding comes from. I'm really saddened for everything we've done with phones that Erlang isn't somehow standard for developing high throughput systems. I digress.
Larry Tesler and others were working on, "Actionable Programming" in the late 80's which I think is now referred to as, "Programming by Demonstration." There currently (prove me wrong here) a comprehensive system where-in the actual computation that takes place can be, "recorded" and, "played back" with arbitrary constraints applied to which (depending on constraints), "timeline" (consider branching web histories) the computer ends up, "deciding on." If memory serves the last time.I was at the Viewpoints website Alan Kay was working on something to do with ontologies. There definitely is a way forward.
"Computer I want you to display to me a system of constraints. Based on this constraint what might be the possible behaviors of the system in the future; of all of these constraints which most fits the criteria. Return(Critera)"
There's a demo by Bret Victor ("Inventing On Principle") where he actual demonstrates this kind of thing in real life along with other, "future programming" paradigm examples. Definitely worth looking at.
I promise you will not be dissatisfied and believe it or not I got more where that came from. If you're ever in a pinch go look up Brenda Laurel talks on YouTube and be prepared to have everything you've ever thought about computing completely turned upside down.
Respectfully I think you're missing the point; the future is new kinds of programming paradigms emerging. Consider punch cards evolving into the Burroughs 5XXX evolving into compilers evolving into, "live systems" (Smalltalk, Erlang's BEAM) which laterally gives rise to REPL-style interaction which makes the previous "write a tome and let the computer read it and then let you know what it thinks" seems superfluous and antiquated compared to, "the computer is listening and will respond back instantaneously when it is talked to." It's worthwhile to think in those kinds of terms-- we can with historical precedent consider that whatever supersedes current human-computer interaction will probably be along similar lines. I think so far we've gotten to a kind of responsive Cartesian, List-evaluating (wink, wink) object which can respond to our commands and that's where modern L337bro from California coding comes from. I'm really saddened for everything we've done with phones that Erlang isn't somehow standard for developing high throughput systems. I digress.
Larry Tesler and others were working on, "Actionable Programming" in the late 80's which I think is now referred to as, "Programming by Demonstration." There currently (prove me wrong here) a comprehensive system where-in the actual computation that takes place can be, "recorded" and, "played back" with arbitrary constraints applied to which (depending on constraints), "timeline" (consider branching web histories) the computer ends up, "deciding on." If memory serves the last time.I was at the Viewpoints website Alan Kay was working on something to do with ontologies. There definitely is a way forward.
"Computer I want you to display to me a system of constraints. Based on this constraint what might be the possible behaviors of the system in the future; of all of these constraints which most fits the criteria. Return(Critera)"
There's a demo by Bret Victor ("Inventing On Principle") where he actual demonstrates this kind of thing in real life along with other, "future programming" paradigm examples. Definitely worth looking at.
https://www.youtube.com/watch?v=8pTEmbeENF4&ab_channel=JoeyR...