Ir al contenido principal

The Roots of Lisp

The Roots of Lisp

Lisp as the main root of functional languages has a rather confusing way of working, it is as basic as it can be so to write a function without the need for it to be complex can quite confusing like the eval functions presented on the document. Is funny that on this paper I read about interpreters and on my SW Design and Architecture I also learn about interpreters.

I have to thank that newer and improved versions of Lisp have emerged like Clojure that make simple to write functions that are interpreted into all this complex code that was explained just to do something relatively simple.

Enough from complaining about, on the bright side, the benefits from having a simple and basic language is that it can be molded to whatever we want from the ground up (basically like how Clojure or any "upgraded" version of any language came to be) and that is why Lisp is still being so functional and useful even today.

The simple notation that Lisp uses is what give to it the power that makes it so great, from these seven primitive functions which are really simple to understand and manage is that a whole language can be born, I haven't actually look at how the  Lisp functions or even the Clojure ones work but I guess that they are all a complex (depending on the function) chunk of code composed only from these seven primitive operators logically written so that in the end there is only needed a simple function call to do all that heavy work.

It would be really interesting to learn from the beginning how functional programming really works and develop a language of my own although it will be needed a lot of logic with some tedious work, I think that at least it would be easier than to do the same from an object-oriented language like that damn Java.

Comentarios

Entradas más populares de este blog

Language as the Ultimate Weapon

Language as the Ultimate Weapon Regarding the question about "Why is the Nineteen Eighty-Four novel by George Orwell relevant to a student taking the Programming Language course?" I'm not entirely sure how it can be related but I'll do my best. On programming languages it is fairly common to hear a lot of names, Java, C#, Swift, among others; each person has it favorite and when we found that favorite we begin to have a sort of disgust against the others, we may see the pros of them but we focus more on their cons, we wish that our favorite language were the only one in existence and this may be good or bad, depending on each one. As the reading said, some people is more susceptible to some things than others, one may understand a programming language as if it were born with it but to other it may never get the hang of it but no because is dumb, his mind behaves different thanks to the language he chose. This variety in languages is good in which it allows for...

Rich Hickey on Clojure

Rich Hickey on Clojure Clojure and his ability to easily communicate with Java makes it the perfect contender for best language, being able to simply call Java code con Clojure code and looking that they work without trouble at start is something that is rarely seen but that when it does appear, is like when God decides to touch you with all his greatness. Programmers and enterprises have noticed this, that's why Clojure is one of the most well-paid languages on USA. Inheriting from LISP the investigation-oriented theme makes a language that cannot be managed by anyone but when mastered, it really shows its true potential, sadly this isn't enough for making LISP, Clojure or the functional programming in general a popular thing, although Clojure with its JVM implementation and macros seeks to fight the problems that stopped LISP from getting mainstream. Thanks to functions that Clojure has, it makes it way easier and direct to solve problems and to actually combine or to...

Pair Programming

Pair Programming It results outstanding to me that the idea of having a pair or a group of programmers working on the same computer is relatively new to the programming world, the phrase of "two heads are better than one" has been existing from a long time ago prior to computation and it is has been proven to work (also it is quite logical), so why pair programming hasn't shine as it's supposed to be? The only thing that disturbs pair programming is the human factor, humans change their mind but at the same time don't, if they have worked all their lives alone and the results have been good the change to a pair programming will be difficult, they'll think that they are superior than their comrade, the suggestions of the last one will be ignored mostly, no help will be asked, making the pair programming more of a hassle than a good programming method. Other thing that involves the human factor is the interaction with others, maybe we can get along with so...