There seems to be a new language coming out every month, but most of them are surprisingly similar. They tend to focus on instructing the machine on how to do work through a series of ifs, loops, numeric calculation and object creation. To a machine, this is fine. To a human, this is not ideal. Figuring out what code does requires decoding these instructions into a mental model of the result it produces.

While this might have been an acceptable tradeoff in a time where every CPU cycle mattered, it's a bad proposition today when we mostly care about developer productivity and time to market.

Is there an alternative? Is it possible to design a language that puts the human being first, and the machine second?

In this talk Robin, an earlier Elm contributor and the current lead developer of Gren, shares his ideas for the "programming language of the future".