Sorry Dave, I can't do that.

When we think about a way to create something that will run in every equipment we think of JVM. In this case, as programmers we tend to seek for something that will run in everything and in the easiest way.  The problem of this solution is that  the limitations of Java tend to be  useful for some basic problems but not for a compiler.  Why is that? A compiler is a machine that can change many things inside the computer. This means that what we are creating is a bridge between the computer and the human language that we are using.  This bridge tends to have many characteristics that depend on the use that we are gonna give it to.  One of the main characteristics of this bridge is imthat we can choose between the numbers that the computer will have  to understand such as hexa, binary or even octal. These points are important to mention due to the fact that we will need to understand what we are doing and how much presition  we need to have.   Another thing to mention is that we need to u

Nowadays people tend to be more connected to internet due to the development of technologies, such as smartphones and tablets. In this case what we tend to notice is that people need these kind of things to do their everyday activities, but there is a point where the user needs to think: do i really need this app that will use my memory or could I live accessing it through my web browser? In this case the answer we could get could be divided into two groups: the ones that download any app they need and just use it for the day and keep it forever, and the group who access the website. In any of those cases we need to consider any case that these groups answer to. As we have seen in many other clases yo create an app is kind of easy with nowadays technology, where the same programming language can be used to create an app for iOS and Android. But in the case  of a website or a webapp we tend to think just inside a  box of what we can do with this kind of technology. What I mean is that

As far as we have been taught, there are many ways to make a computer understand us. Depending on those, there might be a little easier or harder for us to understand it. A clear example of that was the first time we saw a SIF language, clojure. In this case, and as not a very good programmer it was kind of hard to really understand what we were doing due to the fact that parentheses separate our elements and the order of elements really care. I mean, when we program, sometime we forget that something will process it and how we think about it will define how long it will take and what answer will give, just when we get the correct answer we are happy. That case is not the ideal one because we tend to look for answers and not to really understand what we are doing. In  the case of SIF, I personally think that we need first to understand what we are doing before proceeding.  This is due to the fact that we are not used to think like that,  first the simbol, then the values and what is i