The semicolon wars

As a regular programmer, I sometimes get confused when at the time I’m using different languages for different projects, but ironically that’s how I get to know them better, in fact, that little confusion becomes less notorious.

In this article the analogy of regular languages and programming languages are much more than a simple comparison and I think that it has something to do with my little experience using different programming languages for different projects. If we extrapolate that experience to another where someone can speak in many languages, we might get to notice that there are some kind of “reciprocation” between them and that might not be a simple coincidence.

For many centuries, the language has been an extremely important part of the human development, since historically speaking it has immortally impressed in it little fragments of the meaning of that history; but that doesn’t end there, the language has been and stills being one of the most important tools to get what we want to achieve as individuals, and that applies too for programming languages more than anything else, and that’s because the very essence of programming languages is to get machines do whatever we want.

That actually sounds pretty trivial, and in the practice, that gets to be true, just as we try to speak or write some of our ideas the more we become better at expressing ourselves the more we get to get what we want, and then we do it more and more as it becomes easier.

This also gets more interesting to me when we talk about diversification of the vast whole of languages that exist because in the regard of computer sciences the language means much more when we want to use it to get to do smarter things like data science or big data using ideally any language as an input.