The Promises of Functional Programming

Computer Science development has been changing though the computing history, so is very difficult to understand this kind of absatract problems, evenmore if you have been coding in the same way for years.

Computing and mathematical advantages allow us to create better hardware that help us to develop more sofisticated software. In the 1950s John McCarthy designed a  complete new coding method: functional programming, based on Alonso Church’s mathematical theory.

Functional programming has advantages for parallel programming. In this article the author tries to explain what functional programming is and its differences with imperative programming, for this he used Clojure to give examples about functional programming.

 There are huge differences between both programming methods, but that doesn’t mean that one is better than the other. Each one has its pros and cons, and you should be able to determine when to use one over the other.

The principal funcionality  of functional programming is that you compute by composing functions. A function in a mathematical is something that always return the same output to the same input without any change.  To solve these we cant use variable in our functions instead we use loops that evaluate a function with different parameters over each turn or lap.

References

K. Hinsen. (2009). The Promises of Functional Programming. Scientific Programming. available at: http://webcem01.cem.itesm.mx:8005/s201713/tc2006/the_promises_of_functional_programming.pdf

Comentarios

Publicar un comentario

Entradas populares de este blog

Triumph of the Nerds Part II

The one topic that i found most interesting in this video was how IBM used the inverse-engineering as a strategy to get back in tecnological businesses. IBM was noticing how Apple was growing their company very fast, by the sells of the Apple 2, so their will be able of being part of this competition. As IBM was incapable of producing a whole new computer in less than a year, their use something named inverse-engineering whic is the procees in which you take something that is already desing and start disarming it piece by piece in order to understand how its working and then replicate it. This was legal only if the engierniring you use to disarmed and rebuild the machine were completely "virgin" of the knowledge of the ROM BIOS, the term virgin was refering that you do not have any kind of study or you werent part of the procedure of builduing this machine. This is how IBM was able to build a new machine in less than a year and avoid being lost in this war. But he start
Leer más

The Semicolon Wars

The Semicolon Wars As the author tried to explain at the beginning of his paper, scientists have worked hard to find the "perfect" programming language that describes a problem or a data structure in the best possible way. Given this goal, an endless war has developed in decide which programming language best fits this goal. Which the author considers an unnecessary and ridiculous fight. On the other hand I consider that the programming languages ​​are evolving each one of them to achieve this programming language "perfect" although we can not deny that each of these programming languages ​​are different from each others because they can solve in different ways different problems, although, each one provides advantages and disadvantages. Later in the paper, the author suggests that all programming languages ​​have the same computational power, so that the fight is really in deciding which allows you to express your algorithm, to clarify this, begins to compare
Leer más