Technical Overview of the CLR
I didn't like Java even before I knew how to use it, but I liked some things programmed in that language, Minecraft was a good example, but I always remembered that when I played that game I had to put the game configuration in the low resolution and the lowest possible configuration, because the game needed a lot of resources from the computer, so I couldn't run the game properly and enjoy the play. That was before high-school, but I already liked Computers and some tech things back then, I didn't knew how to program complex applications, but I knew a few things, one of them was related to the game, I knew it was programmed in Java, and in that time we said that the game was so slow because of Java's garbage collector and other stuff, I actually didn't verified this thing until I encounter myself with a open-source Minecraft called Minetest, which was a game programmed with C++ using Irrlicht Graphics Library, and it was a very good "copy" of Minecraft, one of the things that really impressed me at the time I played the game was that these Minetest would perform better as Minecraft, so for that one extra point for C++.
The paper Technical Overview of the CLR explained very detailed why the Java Virtual Machine (JVM) was not the preferred "tool" for creating execution environments, and how the Common Language Runtime (CLR) was even better giving the advantages of Portability, Compactness, Efficiency, Security, Interoperability, and Flexibility. Well, there is another reason for not using Java, I never liked it, but was a good language to start learning with Object Oriented Languages, it's a shame that Android applications are developed with Java, I think there are other alternatives but I think they could be very chaotic to configure and not very supported.
Although I'm not the guru master of C++, I will always put C++ on the top of the programming languages pyramid, well not at the top but close.
References:
Comentarios
Publicar un comentario