Linux kernel source tree
This isn't an anti-Go post. Go is a great language. This is about what I want to understand. I just finished building an L7 HTTP load balancer in Go. It accepts connections. It parses HTTP headers. It forwards requests to backend servers using round-robin. It handles concurrent connections with goroutines. It has health checks. It works. And somewhere in the middle of it working, I realized I didn
Confession: I’m not a walking dictionary. If you test me on textbook IT definitions, I might fail. After transitioning through Law and Banking into Tech, I’ve realized that terminology is often just a high-tech "smoke screen" for professional ego. But for many of us, the problem is deeper: it's about the language of logic itself. In my first year of Law school, I spent nights memorizing the "Theor
Most developers use malloc without thinking much about what happens underneath. This project is an attempt to explore that layer by building a memory allocator from scratch in C. The allocator implements malloc, free, calloc, and realloc without relying on libc’s heap functions. It focuses on: Thread safety Per-thread caching (tcache) Efficient free block management using bins mmap-based memory g
Comments