Language Design and Implementation using Ruby and the Interpreter Pattern

 I have got to be honest, it is a tough read. I had to read it a couple of times because the way it is explained is a little tedious, specially if you know nothing about the Ruby language. 

After reading about it a couple of times I think I got the general idea about what the text is trying to get to, however it was still kind of difficult and a little bit confusing at first glance. 

What the author was trying to get at with the explanations described in the article was the use of a bunch of tools that describe a sorta direct way to translate from a language directly into machine code using the language Ruby and the tools it provides. While the idea is a little bit complex at first, it makes sense since languages like common lisp and Clojure work in the same manner. 

In fact while reading the article some flashbacks of my days of programming Clojure came rushing back as those days were the days I suffered a little bit with the new (at the time) way of creating structures and making the computer do what I want using only list structures and complex ways of organizing the information in order for it to understand what I wanted to do.

I also want to remark the efforts of the author to explain in detail how the framework works so that people like me, who are not at all familiarized with Ruby, can understand after a couple of readings. 

However I would like to suggest the use of less formality in the explanations, as it makes a little bit tedious the lecture and hard to understand, although maybe that was the intention in the first place.

Also I like that the source code and example are open source so that anyone that is interested can read and try the program for themselves.