https://celsojr.com Recent posts on Celso Jr's blog Blazor WASM en-us (c) 2022-current Celso Jr Thu, 02 Apr 2026 00:00:00 +0400 https://celsojr.com/post/pixel-perfect-part-3-png-writer https://celsojr.com/post/16 Thu, 02 Apr 2026 00:00:00 +0400 Part 1 rendered pixels. Part 2 organized them. Now Part 3 makes them real. This post builds a PNG writer from scratch—IHDR, IDAT, IEND, CRC32—using nothing but C# and the spec. No libraries, no shortcuts, just bytes becoming an image. https://celsojr.com/post/pixel-perfect-part-2-oop-render https://celsojr.com/post/15 Wed, 01 Apr 2026 00:00:00 +0400 Encapsulation keeps data hidden. Inheritance reuses logic. Polymorphism lets objects behave differently. This post builds an OOP scene with IRenderable, Shape, and Renderer—then shows how it all collapses to raw loops when it's time to render. https://celsojr.com/post/pixel-perfect-part-1-imperative-render https://celsojr.com/post/14 Tue, 31 Mar 2026 00:00:00 +0400 C# gives you for, if, and byte[]. That's all you need to render a frame. This post strips away the abstractions and stares directly at the imperative loop that fills pixels—because sometimes the fastest path is the simplest one. https://celsojr.com/post/partition-with-in-csharp https://celsojr.com/post/13 Fri, 13 Mar 2026 14:00:00 +0400 F# gives you partitionWith out of the box. In C#, you can keep the same semantics with a tiny helper that preserves intent and keeps the call site clean. https://celsojr.com/post/memory-regions-virtual-memory https://celsojr.com/post/12 Fri, 01 Aug 2025 12:00:00 +0400 Learn how virtual memory powers modern games and engines—streaming massive textures, improving stability, and simulating memory beyond RAM using paging, swap files, and on-demand loading. https://celsojr.com/post/memory-regions-registers https://celsojr.com/post/11 Wed, 16 Jul 2025 12:00:00 +0400 What makes CPU registers so fast? This post explains their role, how they differ from cache, and why modern runtimes and compilers use them for top performance—with real C and assembly insights. https://celsojr.com/post/memory-regions-cache https://celsojr.com/post/10 Wed, 25 Jun 2025 12:00:00 +0400 Cache is fast, temporary memory that speeds up access to data by storing what's used most—making systems feel snappy. https://celsojr.com/post/memory-regions-code-segment https://celsojr.com/post/9 Sun, 23 Feb 2025 12:00:00 +0400 The code segment, or .text segment, is a read-only region of memory that contains the compiled machine code of a program. https://celsojr.com/post/memory-regions-static https://celsojr.com/post/8 Sat, 22 Feb 2025 12:00:00 +0400 Static memory, like a public notice board, stores global and static variables for a program's lifetime. It's efficient but can risk memory leaks and bugs. https://celsojr.com/post/memory-regions-heap https://celsojr.com/post/7 Fri, 21 Feb 2025 12:00:00 +0400 The heap offers flexible memory but lacks automatic cleanup. It's larger yet slower than the stack, and mismanagement can lead to leaks and performance issues. https://celsojr.com/post/memory-regions-stack https://celsojr.com/post/6 Thu, 20 Feb 2025 12:00:00 +0400 Stack memory operates in a Last In, First Out (LIFO) manner, making allocation and deallocation fast and automatic, but it has a limited size and can cause stack overflow if exceeded. https://celsojr.com/post/memory-regions https://celsojr.com/post/5 Wed, 19 Feb 2025 12:00:00 +0400 Memory management is crucial in programming, affecting performance and stability. This series explores key memory regions—stack, heap, static/global memory, code segment, cache, and registers—to help developers optimize allocation and avoid common pitfalls. https://celsojr.com/post/closures-performance-implications https://celsojr.com/post/4 Thu, 25 Apr 2024 12:00:00 +0400 If you're coding in a resource-saving mission-critical way and want to avoid the default closure capture for any reason, consider reading further. https://celsojr.com/post/closures-lifting-the-hood https://celsojr.com/post/3 Wed, 24 Apr 2024 12:00:00 +0400 Closure is not something new. In fact, closures has been around for several years. Pretty much all programming languages have closures. https://celsojr.com/post/avoiding-boxing https://celsojr.com/post/2 Wed, 13 Dec 2023 12:00:00 +0400 Boxing involves allocating memory on the heap for the boxed object. In scenarios where memory usage is critical, minimizing unnecessary boxing helps in keeping memory consumption under control. https://celsojr.com/post/hello-world https://celsojr.com/post/1 Mon, 25 Apr 2022 12:00:00 +0400 Coming back with my blog/site after a short break. Life changes, things change, the only thing that never change is my appetite for technology.