The Semicolon Wars

5 years ago a friend of mine gave me a book as a birthday gift. Yes, as you may guess, it was a programming book, and if I got to be specific, an introduction to C programming language. A 17 year old José Pablo felt like he had some kind of magical book in his hands. My first thought was that this book would contain a step-by-step guide to build my first app. I was wrong. After reading some pages of the magical book all of my fantasy dreams went straight to the trash. But hey, not all of it was bad. I realized that the C language was similar to the way math equations are written.

Having said that, let's start talking about The Semicolon Wars. After reading a 5 page magazine article, that felt more like a typical meal-time debate from a group of programmers, I realized that most of the ideas presented have gone through my mind a lot of times. The differences between most of the programming languages are not that much. Most of them share a way of writing operations and instructions, that makes easier to understand them even if you haven't had experience with one particular programming language. But there are some particular languages wheres it's not that intuitive. For example, as I've already mentioned at the top of this post, my first experience with coding was C. Then, when I got into college I learned Python, Java and Swift. All of them, with their own peculiarities, are actually the same in terms of the way you type them. Even Clojure, that is not that similar to what I learned in the past, was not that difficult to understand after reading some code. 

My final thoughts are that it doesn't really matter the way you have to write the code. Just as when you start learning a new (speaking) language, you just have to get used to some technicalities, that in some way, will give it's own soul to the programming language.