/explore
|
You are here 
|
richardstartin.github.io | ||
| | | | |
blog.maxgio.me
|
|
| | | | | Profiling the CPU allows us to analyze the program's performance, identify bottlenecks, and optimize its efficiency. Have you ever wondered what happens behind the scenes when you run a program and how to account for CPU time for the actual program functions? And even more, how to write such a tool to profile the program? Even though great open-source projects provide continuous profiling with vast support for compiled, JITed, and interpreted, languages, with or without debug info, with or without frame ... | |
| | | | |
andreabergia.com
|
|
| | | | | This post is part of the Writing a JVM in Rust series. In this post, I will discuss how the JVM bytecode works. In the next part, I will go over the RJVM code that executes it. | |
| | | | |
0x44.cc
|
|
| | | | | [AI summary] The article provides an in-depth explanation of reverse engineering concepts, including CPU operations, memory representation, data structures, and disassembly techniques. It guides readers through understanding machine code, endianness, signed integers, and how to analyze C code using tools like Visual Studio and disassemblers. | |
| | | | |
ashishvegaraju.com
|
|
| | | In my last article about Functional domain modeling, I explored the expressiveness of F# in modeling a domain. I fell in love with the simplicity and expressiveness of the language. In this article I will attempt to explore function purity in F#. In F#, functions are first class citizens because it allows to pass function as an argument to other function, return a function or assign function to a variable. Initially I found it a bit hard to wrap my head around the concept of treating functions as first class citizens. In fact one of the biggest challenge for me was surprisingly not the weird syntax of F#, but to think in terms of functions. | ||
