The Hundred-Year Language

For me, this article seemed extremely repetitive for the things that it wanted to express, just giving more and more "examples" and over explaining the same concepts one, two or even three times, not only making it really slow, but also having us reading about how would the 100 years language would be, with the same 2 declarations. The future's language will have less "waste of time" for the programmers, and will have the least axioms for the basis of this language.

One of the most interesting topics that are treated is for the programming languages not been able to evolve at the same rate that the general technology are doing. This makes a little more easy to explore the possibilities for the future 100 years, but have the issues that are described, like to not knowing if even the programming languages will still exist then. Even considering the complexity of this labor, the basis that this article takes for concluding that the way of programming it's actually developing around the inefficiency but giving the programmers more tools and flexibility at the time of programming.

An interesting point made and that I thought that could be relatable to the third and fourth generation of programming languages is the concept of not having this rigidity at the data structures, but having the best performance available. As stated by the author, the computers are becoming more powerful every year, and it's a fact that this won't change at least in the near future, and even when this opens the door for more waste, as is said into the article, also I think that that will give us the opportunity to get every time more memory and performance dependent problems to get solved, and with this in mind, not to marry us with the idea of having simplified languages, but to take advantage of the "more complex" languages and get all the potential for the programing to shine at it's best.

Comentarios

Publicar un comentario

Entradas más populares de este blog

Introduction

Hello everyone, well, going fast: my full name is Natanael Pérez Bucio and I'm currently studying the Computer Science major at Monterrey Institute of Technology, the Mexico's State Campus. I've been studying at this campus for 6 and a half years. Even when I've decided to study an TI focused major I had several options based in my interests, having as options a Film Major, a Mathematics Major and even a Philosophy Major. Finally I decided to study Computer Science because I felt more secure in my programming and understanding skills, also is one of the topics that few people understand and it may be a really important advantage for my professional life; it's really polymorphic and give enough options for professional growth on any matter. About my hobbies and my topics of interest I can tell you that I love movies, specially the cult, the independent, the social criticism, the mockumentary and the superhero movies; but I enjoy looking at any movie. R
Leer más

Making Compiler Design Relevant for Students who will (most likely) Never Design a Compiler

This article is pretty interesting, mostly for the nature of the topic that it's treating, and it's curious the focus on the utility around having a compiler design course. The first interesting thing for me is the intention of the author around giving "real life" examples for applications of the knowledge that you can obtain into the compiler's course. The first example that the article gives us is the usage of translation as the base for interesting programs, being the first one translating plain text into graphics, this one is very clear even having some phases just the same as the ones that we get in the compiling process, having as utility to understand this process in order to facilitate the solution of the graphics problem. Just in the same thinking line we have the translation from a LaTeX document formatting to an HTML format. Even as described, that this problem has not the same "translating phases" but even with that, at least the initial
Leer más