top sections

Software re-engineering part I

FeaturedSoftware re-engineering part I

The software field is prone to experience ideas driving to the unnecessary consumption of vast amounts of energy. An energy, as everyone should remember, that in the current scenario causes dangerous pollutants toward the atmosphere or extreme risk like thermonuclear based plants.

Not so long ago electricity was another misunderstood energy and believed to be more a miracle than a technical tool. Today, the lack of legislation to propose rational procedures ends with realities that don't help consider the current sector specially efficient. For instance Android based operating systems, the world's most popular mobile platform in 2014, use an interpreted language causing a not really surprising speed decrement up to 8x-100x compared with other available methodologies like native programming.

A vehicle running 1 km/h instead of 100 km/h because by configuration, there's some class of engineering that makes it breaking. The benefits of using a "virtual machine" —it could be called a "breaking machine" as well— are normally explained with the argument that the programmer needs only to write a unique program for running on different platforms. The virtual machine takes the code and delivers it to the operating system, in any platform. This way it would seem more convenient for the companies that invest on development and find a viable methodology to reduce costs, even if it causes problems to the users in terms of battery consumption or overall responsiveness. Psychologically it's also very sad to have a powerful microprocessor tamed by wrong decisions that charge the worst part to the clients that buy the devices. Working with the device, waiting for it.

Rate this item
(0 votes)
Comment article
Bookmark This Page