Ir al contenido principal

Dick Gabriel on Lisp

A.I. has been the pinnacle of computer science ever since the Turing’s machine, and the first premise to supporting that is “with a machine with infinite resources is possible to transcend Turing’s computability” (V. Müller, 2014).
According to Dick Gabriel in the podcast Lisp was a programming language that was developed around 60’s and it was mainly oriented to the study and development of artificial intelligence. For the time, the structure of lisp was more common for those that studied Turing’s machine given by the fact that its structure was strongly related since its main data structure was the List which remind me to the tape used for Alan’s machine. The basic use case for the List as a data structure was to use a defined language or dialect that they were meant to process via a macro.
Gabriel also said that the Lisp paradigm was “made” the way it was with the unclear intention of making A.I. developers the only ones that can make A.I. research, but that is something that still happening today even with the vast adoption of Open Source for the main languages that are most commonly used for anything (internet helped a lot for that).
When someone thinks about A.I. nowadays, the first thing that comes into mind is a very complex and sophisticated machine that is kind of magically aware of itself, and all sort of things given by imagination. More ironically, in movies and tv shows even when they do remark this stereotype, and they also remark the fact that it is actually a powerful machine that runs a code that makes it look, sound or feel like a person, and that began before a term like “machine learning” was properly conceived.
The idea of using lisp nowadays can be inconceivable for most programmers, because the actual field of study for machine learning and A.I. is now more populated with some other languages.

Reference:

V. M. (2016). Computing and philosophy: selected papers from IACAP 2014. Cham: Springer.

Comentarios

Entradas más populares de este blog

Revenge of the nerds

When I was beginning the path to become a software engineer I tended to magnify the problems related to the things I wasn’t very much involved into, because of inexperience. The Analogy of the pointy-haired boss can apply to many people when they are neophytes to some regard. In the real world it’s something that have happened to me almost every time when the requirements for some software are very ambitious and a pseudo-informed client is involved. Everybody loves standards, it makes things easier and faster, but also is not always wat everyone needs for achieving their goals. Maybe the client wants the latest and greatest revision of a software that is commonly used for their branch in business, but maybe that version of that software implements functions and new paradigms that are no longer the principal need for the client. These kind of concerns are common because where there is money involved, there is always the need to have security and robustness, but in the software deve...

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...

The Promises of Functional Programming

The article “The promises of functional programming” written by Konrad Hinsen highlights how software development has undergone significant advances as much as advances in technology and computational hardware, in the same way the article describes what is the essence of functional languages, what gives life and the reasons why they are created, in parallel it also explains the advantages of using it. The first feature to highlight functional programming is in the use of functions, since unlike the use of mathematical functions, the variables are not part of the functional programming paradigm which according to the article is the first surprise faced to the ones that are starting to use functional programing. One of the other features for the functional paradigm is the built-in fail safe mode against race conditions which is the lack of counter and side effects, and the possibility to define the language itself. Hand in hand with this change also highlights the difference in th...