Clojure
This article was a good review of somethings we already have a notion of after using Clojure, I personally don’t see the big difference still vs and imperative programming, surely it is because all we have done are simple short programs that Clojure excels at, probably longer more complex programs will have a steeper learning curve or be more awkward for the lack of variables but until now is not so different from the first time we saw recursion in object oriented.
The thing that most captured my attention was the last paragraph of the article, I had expectations of a highly parallelizable automatic language, from the way functional programming worked it seemed to me to be the case, but I didn’t consider what was mentioned through the lecture and picked up at the end, the code at the end must be translated to a imperative language because that's how machines work, at the end of the day the language is an advantage in lines of code or simplicity of the program, but most likely faces the sames problems that imperative faces at the end of the day, so it was a little slap in the wrist to come back to reality and don’t expect difficult problems to be solved so easily without effort.
Hmm now I think of Clojure more like an alternative rather than a complement, I think I like it more for small programs that do not consume as many resources but at the end of the day it is nor as ground breaking as I expected, I think its only to be expected at the end of the day it is quite old, although It’s been revised many times and is in many ways a modern language its not the one to rule them all .
Comentarios
Publicar un comentario