Ir al contenido principal

Rich Hickey on Clojure


Rick Hickey really impressed me in this potcast when he started talking about the details of Clojure's implementation of “mutable…ish” data and how he made it happen within the problematic that is the Java Virtual Machine in terms of resources, although the JVM has become more and more efficient within the newer versions; but in that sense the creation of a resource-efficient data structures certainly deserves a lot of admiration from me or anyone that nowadays dedicates its career to data-science because it takes a very clever mind to abstract all those models.
Clojure is presented to you as a new paradigm or tool for your career or projects it can sound super difficult or creepy in the way of syntax complexity, but the truth is that once you dominate it, it becomes another “weapon” in the duty of any computologyst or computer systems engineer.
Clojure is an amazing and powerful language because it is the (almost) perfect link between the objects-oriented paradigm and the unknown (at least for me at the beginning) Functional Programming paradigm as it runs mainly using the Java Virtual Machine, which is platform agnostic by design. Which provides the program a set of data structures and utility functions that can be nonexistent or very difficult to implement into a cleaner implementation of Lisp. Hickey mentioned that Vectors and Maps are unique to Clojure, and it certainly is an interest in terms of the relationship between them and vectors and bijective mappings in the mathematical sense. 
One of the most important barriers in Functional programming from an object-oriented perspective is the lack of variables or directly manipulable data. In my opinion once you overcome this barrier, you can take a really good advantage of all the benefits of it; just like the integrity of information through the function-chain as it does make you a better programmer overall.

Comentarios

Entradas más populares de este blog

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

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

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