|
You are here |
briancallahan.net | ||
| | | | |
mortoray.com
|
|
| | | | | The form a compiler producers before it emits machine code or runs on a virtual machine | |
| | | | |
blog.royalsloth.eu
|
|
| | | | | [AI summary] The article discusses the limitations of compilers in optimizing code and highlights the importance of understanding memory and CPU performance. It argues that modern programming languages are not optimized for current hardware, leading to inefficiencies. The author demonstrates that data-oriented programming can significantly improve performance by reducing memory access and leveraging CPU cache. However, object-oriented approaches are still popular due to their simplicity and historical influence, despite their performance drawbacks. The article also touches on other factors like memory bandwidth, disk I/O, and the importance of data layout for performance. | |
| | | | |
kuterdinel.com
|
|
| | | | | I demonstrate how you can write a simple JIT (Just In Time) compiler for x86 in about 1000 lines of C code. | |
| | | | |
pointersgonewild.com
|
|
| | | The 1980s and 1990s saw the genesis of Perl, Ruby, Python, PHP and JavaScript: interpreted, dynamically-typed programming languages which favored ease of use and flexibility over performance. In many ways, these programming languages are a product of the surrounding context. The 90s were the peak of the dot-com hype, and CPU clock speeds were still... | ||