Code Freely, Live Fully
Code Freely, Live Fully
Moving from C# to Go requires more than just learning new syntax—it requires a mindset shift. Explore how a veteran .NET developer tackled Go's approach to OOP composition, explicit error handling, and interface-driven generics.
Introduction In high-throughput .NET services, allocating and disposing of expensive resources—such as network clients, database connections, cryptographic buffers, or heavy state machines—can quickly trigger garbage collection pressure and latency spikes. While .NET provides basic pooling mechanisms, production workloads often require…
Introduction I have been programming web backends for longer than I care to remember. Up until recently, I used C# extensively because it came closest to the sweet spot I was looking for: a language that was relatively easy to…
Introduction One of Go’s main selling points, at least for me, is its support for concurrency. Starting a go routine is almost ridiculously easy, and channels make communication between go routines a breeze. However, as the saying goes, with great…
Introduction C# has made massive strides in adopting functional programming paradigms over the years. However, there’s one relic that still consistently interrupts clean, fluent data pipelines: the out parameter. If you’ve ever tried to parse a string inside a LINQ…
If you are a C# developer, you have likely tangled with exceptions. While powerful, exception-based control flow can sometimes make your error paths opaque and difficult to trace. Enter the world of functional programming and Rust-inspired error handling. Today, I…
If you are adopting functional programming patterns in C#, you’ve likely discovered the beauty of explicitly defining success and failure states. Wrapping your returns in Result<T, E> or Option<T> forces callers to acknowledge that things might go wrong—or that a…
Introduction In modern Web API development, performance is king, often at the expense of maintainability. If you are still manually passing around pool instances like a hot potato, you are working harder than your code. EsoxSolutions.ObjectPool transforms how .NET develoeprs…
Introduction Most object pools are like a bowl of communal keys: you reach in, grab whatever is on top, and hope it works for the door you’re standing in front of. Usually that is fine. But what happens when you…
Introduction Let’s be honest: handling errors in C# has historically felts a bit like a game of “catch-me-if-you-can” with exceptions and nulls. But as the language evolves, we’re seeing a shift towards more expressive, functional patterns. The Esox.SharpAndRusty library leans…
Introduction Most object pools operate like a simple shop counter: you walk up, ask for an object, and get the next in line. It is efficient, but it is blind. In high-performance systems, “any object” is not always good enough.…
Introduction In a world where users expect sub-second response, the “first-hit penalty” is the silent killer of user experience. We have all been there: the application has just deployed, the first user arrives and… they wait. While the system scrambes…
Introduction In modern .NET development we are often told that the Garbage Collector or GC is our best friend. While true on many occassions, event the best friendships have limits. When your applications constantly instantiates and destroys heavy objects, like…
Introduction Modern C# development often falls into the “Pyramid of Doom” – a series of nested if statements, checking for nulls or success flags which push your actual business logic to the far right of the screen. By using Esox.SharpAndRusty…
Introduction In modern C# development, we often find ourselves lost in “If-Else” chains, nested blocks of null checks and error handling which can obscure the actual business logic. Inspired by Rust and functional programming, the Esox.SharpAndRusty library introduces a way…