![]() ![]() The vast majority of mistakes or oversights that a programmer might make are spotted – and rejected – by the complier, so never make it into the resulting system. Secondly, the Rust compiler – which is responsible for converting the instructions provided by the programmer into a format that the underlying hardware can understand – has incredible power which borders on witchcraft. ![]() įirstly, the syntax of the language (the format and structure of the instructions that the programmer enters ) is designed to make it nigh -on impossible to erroneously write code which leaves the software open to security vulnerabilities, leaving memory in a mess, or creating race conditions (such as ‘catch -22’ scenarios when the program logic grinds to a halt waiting for itself ). Even C # and Go – generally regarding to be pretty efficient – scored 3. In other words, Python consumed over seventy times as much energy as C to do the same job. A paper presented by the ACM ranked 27 programming language in terms of their energy efficiency. This directly translates to power consumption, memory capacity and so on : wasted effort on the part of the computer. However, increased abstraction tends to be accompanied by reduced efficiency – in terms of the balance of ‘useful work’ compared with overhead which the computer has to do. In addition to increased productivity through abstraction and efficient reuse, this evolution helped reliability, security and safety – the ‘runtime environment’ of such languages keeps an eye on what the programmer is doing – reducing the likelihood of ‘shooting themselves in the foot’, tidying up the garbage they leave behind, and to some extent mitigating security risks through erroneous or malicious activities. This started with languages such as C – and then over the decades, gradually developed into languages which mainstream programmers use today – such as Python, JavaScript, C # and PHP. It has gradually become possible to think more about the intention of the software – and less about what was going on under the hood. Over the decades that follow, programming languages have become richer – increasing programmer productivity by simplifying the job. Being a programmer involved thinking like a computer – it was specialist work, laborious and error -prone. ![]() The early days of programming involved writing code which would then be directly processed by the hardware – instructions to the electronics shuffling the zeros and ones around. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |