100 years of knowledge, how will it look like

 Hi everyone, in this week's blog we'll be discussing a very interesting subject addressed by Paul Graham in his essay The Hundred-Year Language. We're presented with the quesiton, how will programs be made in a 100 years time, how will they look like, how will programming languages look like and certain guesses on what they are going to aim for given the resources we assume computers will have by then. 

One feature that stood out to me the most and one that we tend to oversee is simplicity. In an ideal world, we'll be able to write powerful and efficient programs with as little code as possible. Graham gives certain examples such as the concept of numbers being a list of digits, throwing away the idea of strings and making the axiom for a language as simple as possible. This translates into programmers not having to worry about how to optimize the resources they are given, consume time in identifying optimal solutions and letting the hardware handle whatever its given. This is very interesting because Graham poses an interesting argument, now a days it's not so much the resources what are precious to us, but the time of the people implementing the system.  

What I see for programmers and programming languages in a 100 years time alines with Graham's point of view, simplicity as the main concern. Overall user friendliness, adaptability and uniform programming, contextless languages which is something we are already aiming for today with Cloud technology and tools such as Kubernetes. It's how Graham says, it's almost certain that the resources we'll have by then be wasted, but if it's good waste, one that gives us certain liberties while programming to make things easier for us, then it'll not be a waste of resources at all. It's quite intriguing to think about all the different scenarios that could play out, with technology evolving so rapidly, it really is hard to imagine how a programmer will interact with a computer in a hundred years time.