Ask HN: What will coding be like in 25 years?
What do you imagine programming to be like in 25 years?
For example, think about how much more complex it is to develop an Android app versus a web app. All you need to write a web app is a text editor to create three files: an html file, a css file, and a js file. Android development on the other hand is so complicated that you need a fancy IDE to organize everything for you. My prediction for the future is that Android development (and mobile development in general) will eventually become this simple.
Android is actually the perfect example of adding tools to simplify development that end up making development much harder than it needs to be.
You can do so much more with a line of code now and there are so many more ways to make user interfaces, but the fundamental actions of the programmer are the same.
It is the root of many of our difficulties in programming.
If we create very good "program editor" (not text editors) and store our programs as a data object in a database a lot of our current "problems" automatically vanish.
Every node of the program will have a unique identifier so the editor can keep track of it across the lifetime of a project.
We will get automatic version control. Syntax war will end because you will be able to customize the syntax exactly how you like.
The editor can track the association between tests and documentation with the objects in the program.
And so much more. At the moment we share an ASCII language with the compiler. This creates a fundamental tension between the human and the computer.
On one hand we want to specify lots of things about our programs to make it more maintainable and reliable on the other hand we want to keep things easy on the eyes and parseable.
So we create a strong dis-incentive to providing information about the code to the compiler.
Because all we have is a single layer of text which will quickly become polluted.
We need our programs to be able to have lots of meta-data but have an editor that is capable enough to allow us to view what matters at a given time.
This can only be achieved if we stop thinking about programs as lines of text, but rather as data objects.
This is known as "Intentional Programming" if you are interested search for it on Youtube.
Also see Isomorf.io for a basic demo (https://www.youtube.com/watch?v=awDVuZQQWqQ) (I'm not affiliated with them).
Of course text would still be highly involved in the process. But the unit of a program will not be lines in files stored on a file-system.
The program will be a data structure and what the editor presents to you is just a editable projection of that structure.
And that doesn't mean some clunky tree editor GUI with drag and drop either. A sufficiently capable editor could present itself to you almost like a text editor but under the hood it would be operating on rich data objects that form the program not on lines of text.
This opens up a lot of opportunities, for example in project navigation. You could label an entire section of the program as something (example: "Create user") then the editor could give you nice fold/unfold features you could incrementally dig down and navigate the program that way.
You could tag objects in the program with stuff (example: tag a set of functions with the business topic that they deal with).
Because the editor accurately tracks meta-data related to program objects, for example it could be always aware of documentation related to a particular section or function in the program.
So that editor could give you a shortcut to instantly switch to a "documentation view" or "test case view".
I know some of this stuff is already sort-of possible with smart IDEs but they are still quite fragile and inaccurate and easily tricked as they rely on fragile tricks and heuristics to associate things with each other or they rely on conventions that pile up on top of each other and conflict with each other (file naming conventions to indicate something is a test case, etc...).
Treating programs as data objects gives us a strong foundation upon which we can make these fancy features with ease and high accuracy so that you can let your guards down and trust the editor to always be correct.
Thanks for the links, this was the first time I've heard of intentional programming. Neat idea!
Data storage for a demo of something like that is not really hard. Something as simple as a json object would work fine.
One hard part is to make it tolerant of incomplete/invalid objects.
If it's sufficiently tolerant you could make it look very similar to a normal text editor but it would have magical powers under the hood.
You could do all sorts of cool text-editor-like features but because you have a much richer object under the hood you could be much more magical.
The concept of "file" stops having any significance. You'd think in terms of your domain logic and program objects.
So your sidebar project tree could be organised arbitrarily (not dictated by the file system).
You could do fancy keyboard shortcuts. Imagine with key up/down you navigate around a list of objects that are highlighted (like functions). While the function is selected you'd press "d" and bam out pops the function documentation (because documentation would be an attribute of that function and tightly attached to it).
You'd type "h" and see the entire history of that function from day 1, who created it who worked on it, etc...
"r" and it asks you for a new name (name could be a phrase like "login the user into the system" because no text-parsing).
When you enter an entry is added to the history of that object (it has a unique id) "[timestamp] greenyouse renamed this function to 'login the user into the system'".
Then imagine the possibilities for CI/CD.
You could have constraint-based deployment and integration.
For example if any objects in the program tagged with 'security' have been created/modified/deleted you could require stronger code review sign-off etc...
You could "query" the diff of a software revision and do stuff based on that. For example all your "SQL query" nodes would have a pre-determined type.
So when a new revision is pushed you could tell if new SQL queries have been introduced in the system you could notify the database team "Revision #458 has introduced the following 3 SQL queries (click to view)".
Depends how fast automation/AI will grow within the development field.
Isomorph is really cool, but it's a "next 5 years" (or not) – not 25 years.
The future will be declarative. It'll allow voice input, possibly as the primary modality. Objects and functions will be passe.
IOW, describe what you want the program to do, then we'll refine (i.e., sculpt the details together).