New pages

15:1815:18, 14 November 2025 Rust Won’t Replace C++ (and That’s Okay) (hist | edit) [11,965 bytes] PC (talk | contribs) (Created page with "TL;DR: C++ isn’t going anywhere. Its ecosystem, legacy, and embedded presence are irreplaceable. Rust shines as a complement — a way to introduce strong safety guarantees, fearless concurrency, and modern tooling in places where it matters most. The win isn’t replacement; it’s interoperability and risk reduction. The honest bit nobody likes to say out loud Every few months my timeline erupts with “Rust will kill C++” hot takes. It’s entertaining —...")
15:1615:16, 14 November 2025 Why I Stopped Using Clean Code: Rust’s Compiler Enforced All My Best Practices Anyway (hist | edit) [6,751 bytes] PC (talk | contribs) (Created page with "Clean Code did not fail me. Rust simply made it feel redundant. For years I treated Clean Code like scripture. Long method? Refactor. Vague name? Rename. Too many branches? Extract strategy. It helped. My pull requests looked neat. My teammates respected the discipline. Yet production still threw null pointer errors, race conditions, and weird state bugs that no naming rule could save. Then I wrote one small service in Rust, and the compiler started arguing with...")
15:1415:14, 14 November 2025 Why Companies Are Rewriting Code from C++ to Rust (Case Studies) (hist | edit) [6,073 bytes] PC (talk | contribs) (Created page with "Three months back, our principal engineer walked in with a laptop and that look. You know the one. Two charts, both red. Our media pipeline — five years of careful C++ — had started falling over twice a week. Hard. Crashes we couldn’t repro locally, races that only appeared when traffic got spicy. “We should move this to Rust,” she said. I grinned, the annoying kind. “Rewrites are what teams do right before they run out of money.” Switching languages mid-fl...")
15:1015:10, 14 November 2025 Building Native Desktop Interfaces with Rust GPUI: Part 4 (hist | edit) [19,604 bytes] PC (talk | contribs) (Created page with "The State Management Question Three posts built a functional desktop application from first principles. We started with a simple modal dialog, added real text input with cursor blinking and keyboard navigation, then integrated with operating system preferences to respect user choices about appearance and behavior. The biorhythm calculator works. It responds instantly. It looks appropriate on every platform. But the question hanging over all of this is whether the approac...")
15:0915:09, 14 November 2025 Target Triples Explained: How Rust Builds for Everything from ARM to x86 64 (hist | edit) [8,351 bytes] PC (talk | contribs) (Created page with "If you’ve ever peeked into a Rust project’s target directory or tried to cross-compile for a Raspberry Pi, you’ve seen something like this: x86_64-unknown-linux-gnu aarch64-apple-darwin armv7-unknown-linux-musleabihf At first glance, they look like gibberish — random combinations of letters and dashes.  But these short cryptic strings are the DNA of your Rust binary. They tell the compiler exactly what kind of world your code will run in. Let’s break...")
15:0715:07, 14 November 2025 Inside a Rust Memory Safety Failure: The $10K Bug That Shouldn’t Have Happened (hist | edit) [8,993 bytes] PC (talk | contribs) (Created page with "Rust promises memory safety. It sells itself as the language that can’t segfault, can’t double-free, can’t leak unsafe behavior. Press enter or click to view image in full size I believed that too — until one quiet Tuesday morning, when a single unsafe block brought down a production service and cost us nearly $10,000 in customer credits. 1. The Calm Before the Crash We’d built a microservice in Rust for log processing — small, fast, clean. It took JSO...")
15:0515:05, 14 November 2025 4 Times Rust’s Borrow Checker Saved My Code From Disaster (hist | edit) [9,369 bytes] PC (talk | contribs) (Created page with "That sentence is not an exaggeration. It is a snapshot of what safe-by-default code looks like when reality bites. This article walks through four real, compact examples where the borrow checker acted like a safety rail, a referee, and an early-warning system all at once. Each example has clear code, a short benchmark or outcome, and a hand-drawn-style architecture diagram that reveals why the bug would have been catastrophic in other languages. Read this like a develo...")
15:0315:03, 14 November 2025 Inside GATs (Generic Associated Types): Why Rust Needed Them (hist | edit) [10,251 bytes] PC (talk | contribs) (Created page with "In Rust, you can feel the compiler breathing down your neck sometimes. You try to write something elegant, reusable, and “generic”… and suddenly you hit that wall — lifetimes, traits, and type parameters just refuse to fit. For years, that wall was most visible in one particular pain point: async traits and iterators. Everyone knew what we wanted: traits that could return types depending on lifetimes or generics. But Rust just didn’t have the machine...")
15:0115:01, 14 November 2025 Google Cloud Pub/Sub with the Rust SDK and Gemini CLI (hist | edit) [10,226 bytes] PC (talk | contribs) (Created page with "This article leverages the Gemini CLI and the underlying Gemini LLM to develop native compiled code built in the Rust Language for using Pub/Sub messaging with Google Cloud. A minimally viable Pub/Sub connection is built in native Rust code for testing remote messaging to Google Cloud Pub/Sub using the official Google Cloud Rust SDK. What is Rust? Rust is a high performance, memory safe, compiled language: Rust A language empowering everyone to build reliable and effici...")
14:5814:58, 14 November 2025 Rust and SQL: A Match Made in Backend Heaven (hist | edit) [6,687 bytes] PC (talk | contribs) (Created page with "So you’re building a backend API. You need a database. You want it fast, safe, and not a nightmare to maintain. Let me tell you about something that just works: Rust with SQL. The Problem with Traditional Approaches Ever written code like this in JavaScript? const user = await db.query("SELECT * FROM users WHERE id = " + userId); Looks innocent. But if userId comes from user input, you just opened the door to SQL injection. Oops. Or maybe you’re using an ORM th...")
14:5614:56, 14 November 2025 Is the Garbage Collector the Bottleneck? Rust Futures vs. Go Goroutines in High-Throughput Services (hist | edit) [5,884 bytes] PC (talk | contribs) (Created page with "I push traffic until a clean service trips at 40k rps, and dashboards light up with GC on the blame line. The heap grows between bursts; p95 spikes by a third; throughput wobbles without CPU saturation. Rust looks smug with zero-runtime GC; Go looks guilty by association. I track the churn and find a different villain hiding behind allocations and sticky threads. Here is where the bottleneck actually lives. GC blame versus real allocation churn Under bursty load, short-...")
14:5414:54, 14 November 2025 We Shipped Banking-Grade Rust On A “Dead” Crate — 7 Safety Checks That Matter (hist | edit) [8,330 bytes] PC (talk | contribs) (Created page with "Payroll deadline in 47 minutes. ≈$7 million hung behind a transform that lived inside a crate GitHub called “inactive.” My team looked at me. “Are we really shipping on that?” We did. And we slept that night. Not because we’re brave. Because we built the conditions where courage wasn’t required. The Moment The Default Flipped Two hours earlier, staging had looked clean. Then traffic spiked on prod. The one thing between us and missed salaries wa...")
14:5114:51, 14 November 2025 Rust’s Polonius Project: The Future of Lifetime Analysis (hist | edit) [8,737 bytes] PC (talk | contribs) (Created page with "There’s a running joke in the Rust community: “If you think you understand the borrow checker, it’s because you haven’t met Polonius yet.” For years, the borrow checker has been both Rust’s proudest triumph and its biggest pain point. It’s the invisible guardian that ensures your program won’t dangle a pointer or mutate something twice. But it’s also the reason so many new Rustaceans stare at compiler errors muttering, “But… it should work!”...")
14:4914:49, 14 November 2025 Our Rust Rewrite Improved Performance 12X But Killed Team Velocity by 65% (hist | edit) [16,460 bytes] PC (talk | contribs) (Created page with "The pull request had 47 approving comments. “This is beautiful code,” someone wrote. “Poetry in motion,” said another. Our API response times dropped from 340ms to 28ms. Memory footprint? Down 80%. I should’ve been celebrating. Instead, I was staring at my team’s Jira board. Zero story points completed in three weeks. Our best senior engineer had just scheduled a “career conversation” with me. And our CEO kept asking why features that used to take two we...")
14:4514:45, 14 November 2025 Before You Write Another Line of Rust, You Need to See This Optimization Tip (hist | edit) [6,280 bytes] PC (talk | contribs) (Created page with "You’re about to type your next function in Rust — but pause. What if you could write code that runs faster, uses less memory, and scales smarter, all without resorting to crazy hacks? I’ll show you a game-changing tip that many Rust developers overlook, but once you adopt it, you’ll wonder how you ever coded without it. 1. The moment of truth: Why this tip matters When you pick up Rust, you’re already getting a fast, safe language. But speed doesn’t just...")
14:4314:43, 14 November 2025 Will Rust Kill Go in Backend Work, or Is That Just Hype (hist | edit) [5,258 bytes] PC (talk | contribs) (Created page with "Everyone loves a winner until the pager rings. I ship the same API in Rust and Go, then drive load until p95 twitches and memory climbs. Rust holds shape longer. Go ships faster. The charts do not agree with the hype, and that is where the real answer starts. Where Rust actually wins in services When I squeeze latency and memory at the same time, Rust stays calm. Borrowing rules feel strict on day one, but they remove whole categories of bugs that show up under bursty tr...")
14:4214:42, 14 November 2025 Memory Race Conditions That Rust’s Type System Can’t See (hist | edit) [8,194 bytes] PC (talk | contribs) (Created page with "Rust has built its entire identity on safety. Its marketing tagline — “fearless concurrency” — is both a promise and a challenge. You write Rust, and in return, the compiler guards you from segfaults, dangling pointers, and data races. But what if I told you there are race conditions in memory that Rust’s type system can’t see? Yes, the compiler can protect you from data races, but it can’t protect you from logic races, atomic misuses, and cross...")
14:4014:40, 14 November 2025 The 7 Stages of Learning Rust: From Rage to Zen (hist | edit) [7,271 bytes] PC (talk | contribs) (Created page with "The 7 Stages 1) Denial — “It can’t be that strict.” You write idiomatic C++ (in your head) and paste it into Rust. The compiler returns a sonnet about borrowing rules. You skim it; it was a short novel. Typical thought: I’ll just use mut everywhere, how bad can it be? 2) Anger — “Why won’t it let me do the thing?!” You meet move, borrow, mutable borrow, and a mysterious 'static that is not about concerts. You try to hold a slice and modify th...")
14:3814:38, 14 November 2025 Rust vs Go: Garbage Collector vs Ownership — The Memory Showdown (hist | edit) [13,514 bytes] PC (talk | contribs) (Created page with "P95 creeps. CPU warms. Dashboards start drawing little waves where you wanted a flat line. The question hits: is this coming from Go’s collector doing its housekeeping, or from the way your Rust lifetimes are set up? Under pressure, both languages are safe in different ways. One cleans in the background. The other refuses to take off until your seatbelt clicks. This is the head-to-head I wish someone had handed me: what actually happens to memory when real traffic arr...")
14:3514:35, 14 November 2025 How Rustup Manages Toolchains Without Breaking Your System (hist | edit) [8,775 bytes] PC (talk | contribs) (Created page with "If you’ve ever installed multiple versions of Python, Node, or Java on the same machine, you know what real pain feels like.  Environment conflicts. PATH nightmares. “Which version am I even using?” chaos. Rust, though, quietly solved this years ago — with rustup. Rustup is the unsung hero of the Rust ecosystem. It’s the thing that makes installing, updating, and switching between compiler versions feel like magic. You can use nightly, stable, and beta...")
14:3214:32, 14 November 2025 Do You Really Need Tokio? Rust Async That Ships Faster (hist | edit) [5,850 bytes] PC (talk | contribs) (Created page with "What Snapped Me Out Of The Default For a long time my muscle memory was the same: new Rust service, add an async runtime, wire the pieces, feel safe. It looked polished on day one. On day thirty, the team still hesitated to touch core code. Every change dragged through futures, Send/Sync edges, and “don’t block the reactor” warnings. Then I sketched the hot path. One inbound request. One outbound call. One database write. No fan-out, no streams, no fleets of sock...")
14:3014:30, 14 November 2025 The Day Rust Gets a JIT: How Cranelift Could Change Everything (hist | edit) [11,714 bytes] PC (talk | contribs) (Created page with "If you’ve ever built large systems in Rust — from compilers to web servers to data pipelines — you’ve probably accepted one truth: Rust is fast, but it’s frozen at compile time. Once you build that binary, it’s done. It doesn’t adapt, optimize, or recompile itself at runtime. It’s static, predictable… and sometimes, just a little too rigid. But what if Rust got a JIT compiler — a Just-In-Time engine that could take Rust code, compile it at runtim...")
14:2814:28, 14 November 2025 Building Native Desktop Interfaces with Rust GPUI: Part 3 (hist | edit) [23,571 bytes] PC (talk | contribs) (Created page with "Native Look Parts 1 and 2 built a functional application. We have windows, input fields, validation, keyboard navigation, and smooth cursor blinking. The interface works, but it doesn’t quite belong. The colors are hardcoded. The accent blue we chose looks fine in light mode but clashes in dark mode. Users who’ve set their accent color to purple or green see our blue anyway. The application ignores the preferences they’ve already expressed through their system s...")
14:2314:23, 14 November 2025 Java vs Rust: I Rewrote Our App and Saved My Company $2M/Year (hist | edit) [9,493 bytes] PC (talk | contribs) (Created page with "I didn’t bet on a language. I bet on shape: one hop, strict backpressure, lean memory. Rust helped enforce that shape. Java (with virtual threads) stayed where our team moves fastest. The win came from how the work flows, not what the syntax looks like. I’m going to show you the map, the code, and the numbers. Then you can steal the shape for your stack. What Was Breaking (And Why It Hurt) Traffic grew faster than our discipline. Latency spikes arrived in waves...")
14:2014:20, 14 November 2025 Rust Futures vs. Go Goroutines: The Ultimate Async I/O Performance Showdown (hist | edit) [5,402 bytes] PC (talk | contribs) (Created page with "I ran the same load test against two servers handling real async I/O work. One used Rust with Tokio futures. The other used Go with goroutines. Both promised effortless concurrency, but the memory graphs told different stories. When traffic spiked past 5,000 connections, one service stayed lean while the other ballooned to twice the footprint. The throughput gap was smaller than I expected, but the predictability gap was not. How Each Model Schedules Work Under Pressure...")
14:1914:19, 14 November 2025 The $25,000 Rewrite: Rust vs. Go — Which Service Cut Our Cloud Bill by 70%? (hist | edit) [6,015 bytes] PC (talk | contribs) (Created page with "We stared at a monthly bill that climbed faster than traffic. One backend service ate most of it, and scaling rules hid the real reason. We rewrote it twice, once in Go and once in Rust, and then measured under the same load. The answer was not language pride; it was how each stack handled concurrency, I/O, and memory churn. The story got interesting when the counters stopped arguing with each other. Where the money actually leaked on requests We chased CPU first, then...")
14:1814:18, 14 November 2025 Why Rust Needs Explicit Lifetimes (Even When the Compiler Is Smart) (hist | edit) [8,913 bytes] PC (talk | contribs) (Created page with "If you’ve ever stared at a wall of 'a, 'b, 'static and thought “surely the compiler could figure this out,” you’re not alone. Rust’s borrow checker can see the shapes of your references and it will prevent use-after-free. So why does the language still make you write explicit lifetimes? Short answer: safety is why lifetimes exist; clarity, stability, and precise contracts are why explicit lifetimes exist. They’re less about making your code safe an...")
14:1614:16, 14 November 2025 5 Myths About Rust Ownership — And What You Should Really Know (hist | edit) [10,336 bytes] PC (talk | contribs) (Created page with "Rust ownership will make your life miserable. That sentence hurts to read if there is fear in the chest. Ownership is not a punishment. Ownership is a tool that keeps applications safe, fast, and clear. If the rules feel harsh, that feeling is an invitation to learn a few patterns that change everything. This article will strip the myths away. Each myth is short, concrete, and followed by small code, a compact benchmark, and a hand-drawn-style architecture sketch made...")
05:1605:16, 14 November 2025 Developing macOS Applications in Rust (hist | edit) [8,034 bytes] PC (talk | contribs) (Created page with "For training AI models, I use an Ubuntu server with 16 cores alongside a MacBook Pro M4 Max. During training, I frequently monitor CPU and memory usage to ensure all cores are utilized efficiently and to estimate memory consumption. However, I missed having on macOS a system monitor that provides a visualization similar to what I’m used to on Ubuntu. So, I built one — a simple System Monitor application that displays CPU and memory usage. Although it’s easy to d...")
05:1405:14, 14 November 2025 The Ultimate Guide to .NET 9 vs Go vs Rust API Performance in 2025 (hist | edit) [13,501 bytes] PC (talk | contribs) (Created page with "If you’ve been knee-deep in microservices, this error probably looks familiar. I first hit it while stress testing an API gateway that had .NET 9 on one side, a Go service acting as a worker, and a Rust service crunching batch jobs. What started as a simple debugging session turned into a weeks-long performance bake-off across three stacks. The results? Eye-opening. In this post, I’ll share real benchmarks, pitfalls, and hard-won lessons comparing .NET 9, Go, and Ru...")
05:1105:11, 14 November 2025 Rust in Space: How ESA and NASA Are Testing Rust for Flight Software (hist | edit) [5,881 bytes] PC (talk | contribs) (Created page with "“Space doesn’t forgive bugs.” That’s the line a European Space Agency (ESA) engineer once dropped at a conference when someone asked why they were experimenting with Rust. In backend land, a panic takes down a microservice and we restart a pod. In embedded land, a memory bug can crash a drone. But in space?  There’s no SSH. No restart. No debug logs coming back from a Mars rover. Just silence. And $500M worth of hardware drifting in the void. So yeah —...")
05:0805:08, 14 November 2025 Python and Rust in the Modern Programmer’s Toolkit (hist | edit) [7,766 bytes] PC (talk | contribs) (Created page with "For years, Python has held a warm place in my programming world. And why not, it’s the language of data scientists, researchers, and web developers who value clarity and speed of development over raw performance. Rust, on the other hand, has become a rising force among developers who care about safety, concurrency, and control. Python’s runtime is forgiving. You can change types on the fly, pass unexpected arguments, or forget to handle edge cases until runtime. In...")
05:0605:06, 14 November 2025 Rust, Go, or Java? Choosing the Best Programming Language for Your High-Scale System Design (hist | edit) [8,063 bytes] PC (talk | contribs) (Created page with "Production punished my bias the day p95 jumped and the pager would not stop. I had to choose speed, safety, and delivery at the same time. No theory. No brand loyalty. Just numbers and the shape of my system. That is when the choice between Rust, Go, and Java became simple, not easy. You are here because the stakes are real. Traffic grows. Budgets do not. The wrong pick lingers for years. Let me show you when each language wins, how I measure it, and where teams quietl...")
05:0505:05, 14 November 2025 Meet the Rust GPU Ecosystem: WGPU, Naga, and the Future of Graphics Safety (hist | edit) [5,522 bytes] PC (talk | contribs) (Created page with "Let’s be honest: GPU programming used to feel like joining a cult. * Cryptic APIs * Undefined behavior landmines * Segfaults if you breathe wrong * Debugging that makes you question your life choices If you ever hand-rolled a Vulkan pipeline at 2AM and stared into the abyss of VkPipelineLayoutCreateInfo, you know the pain. Then Rust entered the arena. And suddenly the dream didn’t sound so crazy: “What if GPU programming didn’t need to feel like holdi...")
05:0305:03, 14 November 2025 Rust GPUI vs Electron: 5× Faster Cold Starts and 50% Less Memory (hist | edit) [6,090 bytes] PC (talk | contribs) (Created page with "I replaced a familiar tool with a faster one, then watched my laptop cool down. Your users do not care how clever your stack looks. They care about a window that opens instantly. They care about a computer that does not gasp for air. I chased that feeling for months. I tried flags. I tried tree-shaking. I trimmed icons. Cold starts still felt like rush hour, and memory graphs looked like a mountain range. Then I rebuilt the same app with Rust GPUI. The window...")
05:0105:01, 14 November 2025 How to Match a String Against String Literals in Rust (Without Tears) (hist | edit) [5,906 bytes] PC (talk | contribs) (Created page with "If you’ve ever tried to do this in Rust: fn main() { let stringthing = String::from("c"); match stringthing { "a" => println!("0"), "b" => println!("1"), "c" => println!("2"), } } …and been greeted by a grumpy E0308: mismatched types, you’ve run head-first into one of Rust’s sharpest—and most helpful—edges: types matter. Let’s turn that compiler error into understanding and write idiomatic, readable code you’ll be pro...")
05:0005:00, 14 November 2025 How Rust Is Rewriting Databases (TiKV, FoundationDB Clients, Materialize) (hist | edit) [7,060 bytes] PC (talk | contribs) (Created page with "There was a moment in 2021 when I realized Rust wasn’t “just a language” anymore. I was debugging a microservice where our storage stack was doing mental gymnastics — partial failures, async replication, data races in Go code, and a write-path bottleneck that only appeared under 50k QPS load. Then someone from SRE casually said: “Have you looked at Rust-based KV engines? TiKV’s write path never corrupted under crash loops.” That was the day reality snapp...")
04:5704:57, 14 November 2025 Rust Is Cool. But Java Just Did Something Smarter (hist | edit) [6,747 bytes] PC (talk | contribs) (Created page with "For years, Rust has been the darling of the developer world. Fast. Safe. Modern. Every performance benchmark, every systems programming blog, every Hacker News thread — Rust was the language that made Java look like an ancient relic of enterprise boredom. But while everyone was busy arguing about ownership semantics and rewriting everything from kernels to web servers in Rust, Java quietly solved one of software’s oldest problems — and almost no one outside the...")
04:5604:56, 14 November 2025 I Fired My Entire Node.js Stack — Rust Rebuilt It in 3 Weeks (The Ugly Truth) (hist | edit) [12,761 bytes] PC (talk | contribs) (Created page with "Our billing API hit 200k requests per minute during peak hours. Node.js was handling it fine — until it wasn’t. P99 latencies spiked to 850ms. Event loop blockages cascading through the system. Memory usage climbing 40% week-over-week despite zero traffic growth. I profiled everything. Optimized database queries. Threw more instances at it. The core problem: garbage collection pauses during high-throughput operations were killing us. I made the call: migrate to Rust....")
04:5404:54, 14 November 2025 Rust in the Linux Kernel: The Religious War Gets GPU Drivers (hist | edit) [9,743 bytes] PC (talk | contribs) (Created page with "I’ve been watching the Rust-in-Linux saga unfold for years now, and let me tell you: I’ve seen some heated technical debates in my more than two decades of experience in software engineering, but this one takes the cake. It’s not just about choosing a programming language anymore. It’s become what Linus Torvalds himself called “almost religious war undertones.” And you know what? He’s absolutely right. Here’s the thing: I’ve written C code very heavily...")
04:5104:51, 14 November 2025 4 Rust Best Practices Every Senior Developer Swears By (hist | edit) [8,856 bytes] PC (talk | contribs) (Created page with "That is the kind of trade that separates good engineers from senior engineers. Read carefully. Apply deliberately. Ship with confidence. Why this matters right now Rust is fast. Rust is safe. Rust also punishes sloppy design with subtle runtime surprises and build-time churn. The four practices below are the tools senior developers use to turn Rust from a fast language into a predictable, maintainable engine that wins production battles. This is written as if sitting...")
04:4904:49, 14 November 2025 Building Native Desktop Interfaces with Rust GPUI: Part 2 (hist | edit) [21,494 bytes] PC (talk | contribs) (Created page with "Real Input Handling: Beyond Hello World Part 1 covered the basics: components, rendering, event handlers, window management. We built a dialog that appeared, responded to clicks, and looked native. That foundation matters, but it only scratched the surface of what real applications demand. I was originally planning to dip into cross platform aspects to realize that a simple dialog box would not provide enough depth. Real applications need text input. They need validation...")
04:4704:47, 14 November 2025 I Rewrote a Java Microservice in Rust — and Lost My Job (hist | edit) [7,231 bytes] PC (talk | contribs) (Created page with "It started as a weekend experiment. It ended with a meeting invite titled: “Quick Sync — Org Update.” That’s the story of how I tried to be the “10x engineer” who optimized everything — and accidentally optimized myself out of employment. Let’s rewind a bit. 1. The Boring Java Service That Worked Just Fine We had this tiny Java Spring Boot service that handled about 15,000 requests per minute. Its job? Parse a payload, validate it, save a record, a...")
04:4604:46, 14 November 2025 Rust vs DPDK: The New Packet IO Battleground (hist | edit) [9,908 bytes] PC (talk | contribs) (Created page with "There’s a moment every low-level network engineer remembers: The first time you touch DPDK. You feel like you’ve unlocked the secret underbelly of the Linux kernel. Then… you realize you also unlocked a world of pain: segmentation faults, pointer math, NUMA pinning bugs, and 20,000-line CMakeLists. Fast forward to 2025 — and something’s shifting. Rust isn’t just “memory safe” anymore. It’s becoming a contender for high-performance packet IO, standi...")
04:4404:44, 14 November 2025 6 Rust Mistakes That Destroy Performance in Production (hist | edit) [9,293 bytes] PC (talk | contribs) (Created page with "This article saves hours of debugging time and gives back real CPU, latency, and sanity. Read this now if any of the following apply to you: * Production p99 latency creeps upward each week. * Benchmarks look fine locally and fail under load. * There is a part of the codebase that everyone fears to change. The following 2,500 words will outline six actual errors, provide a fix, provide specific benchmark numbers, and demonstrate minimal code to replicate the issue....")
04:4104:41, 14 November 2025 He Promised Rust Would Save Us — It Ended the Company Instead (hist | edit) [6,218 bytes] PC (talk | contribs) (Created page with "It started with a promise. Not a business plan, not a roadmap — a promise. “Rust will fix everything.” We were tired of Go’s race conditions, Node’s memory leaks, and Python’s performance anxiety. Rust sounded like freedom — no nulls, no segfaults, no fear. And honestly? We bought it. I remember the CTO — let’s call him Arun — standing in front of a whiteboard, eyes bright with conviction. “Memory safety,” he said, like it was a religion....")
04:3904:39, 14 November 2025 Rust vs. Go: Why One of Them Will Dominate Backend Development in the Next 5 Years (hist | edit) [5,165 bytes] PC (talk | contribs) (Created page with "Backends do not care about feelings. They care about tail latency. They care about memory. They care about how fast you debug at 3 AM. I have shipped both Rust and Go in production. I have celebrated both. I have cursed both. Here is the uncomfortable truth: one will own most new high-throughput backends by 2030 — not because it is prettier, but because its failure modes are cheaper. The real fight: tail latency vs. time-to-shipping * Rust trades compil...")
04:3804:38, 14 November 2025 Rust vs C++: Performance Benchmarks That Surprised Me (hist | edit) [9,018 bytes] PC (talk | contribs) (Created page with "After two years of writing production code in both languages, I decided to settle the debate with real numbers. The internet is full of opinions about Rust versus C++. Most of them are based on theory, biased benchmarks, or tribal loyalty to one language over the other. I’ve been writing C++ professionally for eight years and Rust for the past two. Last month, I decided to stop arguing and start measuring. I built the same application in both languages — a high-perfo...")
04:3604:36, 14 November 2025 I Upgraded to Rust 1.90 and It Broke My Production App at 3AM (hist | edit) [8,661 bytes] PC (talk | contribs) (Created page with "Editor’s Note: This post originally referred to Rust 1.90.1 the correct version is 1.90. Thanks to Austin Orr for catching that. Correction: An earlier draft implied non-exhaustive match became a runtime error in 1.90. That’s wrong — >E0004 has been a compile-time error for years. Our outage came from an upstream trait change + a bad Copy derive, and we’d suppressed compiler warnings, so the panic slipped through. I was already reaching for my laptop before my...")
04:3304:33, 14 November 2025 The state of SIMD in Rust in 2025 (hist | edit) [9,877 bytes] PC (talk | contribs) (Created page with "What’s SIMD? Why SIMD? Hardware that does arithmetic is cheap, so any CPU made this century has plenty of it. But you still only have one instruction decoding block and it is hard to get it to go fast, so the arithmetic hardware is vastly underutilized. To get around the instruction decoding bottleneck, you can feed the CPU a batch of numbers all at once for a single arithmetic operation like addition. Hence the name: “single instruction, multiple data,” or SIMD fo...")

14 November 2025