/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

www.trevorlasn.com
| | orlp.net
4.9 parsecs away

Travel
| | [AI summary] A deep dive into the complexities and pitfalls of comparing different numeric types (integers and floating-point) across various programming languages and the CPU architecture
| | www.sicpers.info
3.2 parsecs away

Travel
| | [AI summary] The article explains that IEEE 754 floating-point numbers are not inherently weird but are specialized tools, and encourages programmers to explore alternative number representations like decimals and posits for more general-purpose computing needs.
| | arnorhs.dev
3.5 parsecs away

Travel
| | I read somewhere that a bitwise left shift was a faster method of removing a fraction of a floating point number in Javascript than using parseInt or Math.floor(). I wasn't surprised that parseInt was slow, since I think it parses the number as a string, but the left shift being faster than Math.floor() was a bit more puzzling to me. So I decided to make a JSPerf test to compare those three methods. Read on for the full results
| | gpfault.net
30.6 parsecs away

Travel
| [AI summary] The provided text is a detailed explanation of how to write a simple 64-bit Windows application in assembly language that calls the ExitProcess function from the KERNEL32.DLL library. It covers the following key topics: 1. **Memory and Register Basics**: Explains how memory and registers work in 64-bit Windows, including the use of the stack pointer (RSP), registers like RCX, RDX, R8, and R9 for passing arguments, and the importance of stack alignment for performance. 2. **Calling Conventions**: Details the 64-bit Windows calling convention, including how the first four integer or pointer arguments are passed in registers (RCX, RDX, R8, R9), how additional arguments are passed on the stack, and the requirement for the stack to be aligned to ...