Thread 6

Parallelism is a trend that is becoming popular but to determine if going to stay is a bit uncertain at the moment.  The hardware is evolving in a fast pace at the moment, and the demand for programs to take advantage of this hardware is increasing exponentially. The only but big problem for programs to take advantage of this is that it requires people that understand how to implement this solution and also understand how it works. There was a moment that programmers understood in a high level what the hardware would do when a set of instructions is given to it. I am not saying that a software developer needs the knowledge to construct the component , but understanding how it works is essential especially when adopting new technology.  Understanding what the black box do, a concept that can be applied in any type of engineering, especially when we are giving a software system. Yet there was a point where developers didn't have to worry about how the intricate design of hardware worked. They actually stop caring and started to focus on the main aspect of their profession which it was the code. We can see it now in how some developers cannot see the difference between a CPU and GPU. Usually they will attribute the GPU to video games and the CPU as an essential component for any computer that is in charge of executing process. Yet the reality is that GPUs are becoming more and more relevant in the field and they are used in different areas of the industry apart from video games. AI, data analysis , decryption these are some examples on what GPUs are used for at the moment. In matter of fact there are some GPUs especially made for these type of purposes , usually contain more internal ram for more space for different computations. This is a critical example on why understanding the hardware is essential. Programmers are having a hard time to implement parallelism in some languages when it comes to only one CPU, the problem could increase when more components come into play, which is not a far future.  Computers can use several GPUs and is something that us programmers could be facing on programming in the future.

Comments

Post a Comment

Popular posts from this blog

Thread 1

This is the first Post for the multithreading programming class, Hi my name is Arturo Velazquez and I am interested in all the things that are related to some kind of development. Right now I work for an American company called LendingClub as a front end developer. What I expect from this subject is to improve my skils in programming for C++. C++ is a language that i want to dominate and be fluent in with. I have different hobbies when I have time , like playing video games and miniatures.
Read more

Thread 4

The trends for programming will always keep changing doesn't matter in which sector we are focused on. We have seen it through out the years on how different ways of programming have become more relevant in different periods of time. Now the reason for why a trend becomes popular could be for a number of reasons. This could be for development of better technology, easier understanding on the programming part of the development or even the demand of developers on certain language. In this case knowing that parallelism is going to become the next trend that programmers will need to learn. Almost all computers and processors have a dual core integrated to them. So is easy to see that people will try to improve their execution times of programs by using multiprocessors. I think this is becoming more relevant with a new way of computing. Quantum computing will cause a whole revolution on how we understand and solve computer problems. A major problem that will cause with this revolution
Read more

Thread 8

The Erlang programming language is an interesting approach to a solution for concurrent and parallel programming. It is interesting for so many different aspects and the first aspect would be that is a programming language that doesn't require the idea of sharing memory. This is a big change in paradigms , we have seen it in some old languages that the idea to share memory is a common one. Yet even if it is an old idea and a paradigm that is implemented in several languages , is hard to handle. It is true that we have certain objects that could help us to manage the memory and how different threads or programs can access shared resources. This sometimes can be difficult to understand and even sometimes hide some bugs that are hard to replicate and even solve them.  Another idea that Erlang deviates from is the idea of immutable variables or states. This is another old way to manage resources and make sure that we can keep the state of the program appropriately. We can notice that E
Read more