New pages

10:4410:44, 18 November 2025 Borrow Checker Therapy: How Rust Broke My Code, My Ego, and Then Made Me a Better Engineer (hist | edit) [10,022 bytes] PC (talk | contribs) (Created page with "It felt personal. It felt like a code review that would not let me leave the room until the code was right. That lesson cost time and bruised pride. It repaid the investment with reliability that no unit test would have found. This article is the story of that fight. It is practical, opinionated, and full of small examples that show the change. If a single tool can teach better code discipline and fewer production incidents, it is worth listening to. file:Borrow_Ch...")
10:3810:38, 18 November 2025 Is Rust the Future of Programming? Here’s Why You Should Care in 2025 (hist | edit) [5,247 bytes] PC (talk | contribs) (Created page with "The world of coding changes so fast, and every few years, a new programming language steps into the spotlight. 500px Right now, that language is Rust. It’s not just a passing trend; it’s a serious answer to some of the biggest problems we face in software today. If you’re building any kind of modern application in 2025, you need to know what Rust is doing and why it matters to your job and your company’s securit...")
10:2610:26, 18 November 2025 10 Rust Interview Questions You Will Keep Seeing in FAANG Interviews (hist | edit) [11,096 bytes] PC (talk | contribs) (Created page with "500px This article is a focused, practical guide for engineers who prepare for systems-level interviews at top firms. Each question is short, followed by a clear example, a concise micro-benchmark or performance observation, and a small hand-drawn-style diagram where the architecture or ownership matters. Read it as if a senior engineer were coaching you over coffee. The goal is for you to answer confidently, show judgment, and write code...")
10:1510:15, 18 November 2025 The Real Story Behind Polonius: Rust’s Next Borrow Checker (hist | edit) [9,748 bytes] PC (talk | contribs) (Created page with "500px When Rust first introduced the borrow checker, it changed how developers think about memory forever. No garbage collector. No segfaults. Just pure compile-time guarantees. But the deeper people went, the more edges they found. Lifetimes that refused to compile. Borrow errors that looked nonsensical. You’d stare at the compiler’s angry red messages, muttering, “But I’m not even using that variable anymore!” That frus...")
10:0810:08, 18 November 2025 Why Memory-Mapped I/O Feels So Different in Rust (hist | edit) [8,463 bytes] PC (talk | contribs) (Created page with "500px When you first hear memory-mapped I/O (MMIO), it sounds like some obscure OS-level trick reserved for kernel hackers. But if you’ve ever streamed a 10GB dataset without loading it all into RAM, or accessed GPU registers directly, you’ve probably used it — even if you didn’t know. In most languages, MMIO feels like a hidden performance optimization. In Rust, it feels like a first-class primitive. And that difference is...")
10:0110:01, 18 November 2025 Stop Using dbg!() in Rust: The Debugging Stack That Saves Hours (and Your Sanity) (hist | edit) [6,377 bytes] PC (talk | contribs) (Created page with "The clock read 2:00 PM. I was hunting a bug deep inside an async service. The error was a classic Rust failure: a deadlock in a concurrent data structure. 500px I did what every Rust developer does when they get desperate: I scattered 40 different dbg!() calls throughout the function. Rust <pre> // My desperate 2:00 PM code: let result = dbg!(calculate_next_state(input)); let response = dbg!(process_response(result)); </pre> That was...")
09:5509:55, 18 November 2025 The Day libc Died: How Rust’s Core and Alloc Crates Work Together (hist | edit) [7,596 bytes] PC (talk | contribs) (Created page with "500px If you’ve ever tried compiling Rust code for an embedded board, a bare-metal kernel, or even a toy OS, you’ve probably hit this cryptic error: <pre> error[E0463]: can't find crate for `std` </pre> That moment feels like stepping off a cliff. Suddenly, your beautiful, safe Rust world — with println!, threads, and files — vanishes. Welcome to the no_std world. But here’s the twist: Rust doesn’t need libc or even...")
09:4909:49, 18 November 2025 What Happens When Rust Meets DMA (Direct Memory Access) (hist | edit) [8,761 bytes] PC (talk | contribs) (Created page with "500px When you write Rust, you feel safe. The compiler guards your memory like a loyal knight — no use-after-free, no data races, no null dereferences. But then… you meet DMA — Direct Memory Access — a hardware-level beast that says: “I’ll just write into memory directly, thanks. No need to bother your borrow checker.” And suddenly, Rust’s guarantees start trembling. This is the story of what happens when Rust’s ownership model ...")
09:4309:43, 18 November 2025 Learning about Rust Benchmarking with Sudoku from 5 minutes to 17 seconds (hist | edit) [13,014 bytes] PC (talk | contribs) (Created page with "500px I’ll take you through the process of optimizing a Sudoku solver written in Rust. We’ll start with a simple, unoptimized version and apply a series of optimizations that will take the time to solve 100,000 puzzles from over 5 minutes down to just 33 seconds, and 20,000 of the hardest puzzles from over 2 minutes down to just 17 seconds. The Setup The project is a command-line Sudoku solver written in Rust. The puzzles are read from...")
09:2909:29, 18 November 2025 Macros 2.0: The Rust Feature That Will Make Your Editor Feel Like Magic (hist | edit) [7,412 bytes] PC (talk | contribs) (Created page with "500px Why I think Macros 2.0 will be one of Rust’s biggest quality-of-life wins — on par with things like pattern types or variadic generics. TL;DR New macro system: define declarative macros with the macro keyword instead of macro_rules!. Real scoping: paths inside the macro body resolve where the macro is defined, not where it’s invoked. Way better IDE UX: hover, go-to-definition, comple...")
09:2509:25, 18 November 2025 The Hidden Magic Behind Box T — How Rust Manages the Heap Without You Noticing (hist | edit) [8,781 bytes] PC (talk | contribs) (Created page with "500px When I first touched Box<T>, I thought it was just a pointer. Something that quietly put data on the heap and cleaned it later. I could not have been more wrong. Box<T> is not a convenience. It is a contract. It turns heap allocation — one of the most unpredictable parts of system design — into something you can trust every single time. And once you see what actually happens inside that one call to Box::new(), you...")
09:1709:17, 18 November 2025 The Most Elegant Code I’ve Ever Written was in Rust (and the Most Painful to Debug) (hist | edit) [6,477 bytes] PC (talk | contribs) (Created page with "500px I wrote 40 lines that felt like poetry. Under load, the poetry became silence. This is a bug hunt diary: timestamps, exhibits, and the small rewrites that made elegance debuggable. Cast * Service: ingest → enrich → cache → publish * Stack: Rust + Tokio, Postgres, Kafka * Metric that mattered: p99 < 250 ms, no stalls 00:00 — Why the code felt… perfect I replaced a chunky pipeline with one composable stream:...")
09:1309:13, 18 November 2025 Singletons in Rust? Yes, and Here’s the Dangerous Way People Do It (hist | edit) [5,667 bytes] PC (talk | contribs) (Created page with "500px If you’ve spent time in Java or C#, you’ve probably seen the Singleton pattern — a way to guarantee that only one instance of a type exists in your program. It’s a design pattern that people either love (“simple global access”) or hate (“global mutable state is evil”). When I first moved to Rust, I assumed singletons weren’t even possible. After all, Rust hates global mutable state. And yet… developers still...")
09:0809:08, 18 November 2025 Unsafe Rust Isn’t the Dark Side. It’s the Only Reason Rust Works. (hist | edit) [5,622 bytes] PC (talk | contribs) (Created page with "Hook Everyone loves to chant the gospel of Rust: memory safety, fearless concurrency, no segfaults, borrow checker as your guardian angel. But here’s the truth no Rust evangelist wants on a T-shirt: Rust is only safe because of the unsafe parts. Yes. That keyword you were told to avoid like it’s black magic? That’s the engine oil. Without it, the whole machine seizes up. 500px The Lie We Sell Newcomers When you first touch Rust, you get...")
09:0309:03, 18 November 2025 One Million Connections, 2GB RAM: Rust’s New Async Runtime Just Rewrote My Scaling Playbook (hist | edit) [7,907 bytes] PC (talk | contribs) (Created page with "The benchmark was not theoretical. It was a pressure test against a real workload. The surprising part was not the number. The surprising part was how little memory it required to hold that state. This is the story of the tradeoffs, the tiny engineering changes that mattered, and the exact pattern that any backend engineer can reproduce on commodity hardware. 500px Why the question matters Most scaling stories are about adding mo...")
08:4708:47, 18 November 2025 Rust Made My Backend Boring — and Now It Handles 10 Million Requests Without Breaking a Sweat (hist | edit) [7,953 bytes] PC (talk | contribs) (Created page with "The first release was chaos. Pages crashed, graphs spiked, and the pager screamed like a fire alarm. The rewrite was calm. No alerts, no drama, no 3 A.M. messages. Now the system quietly serves ten million requests every single day — and I barely think about it. That is not bragging. It is a confession. A confession that for years, I believed complexity was proof of skill. Then Rust taught me that boring is beautiful. file:Rust_Made_My_Backend_Boring.jp...")
08:4208:42, 18 November 2025 Rethinking Concurrency: The Actor Model and Ractor in Rust (hist | edit) [18,533 bytes] PC (talk | contribs) (Created page with "500px The moment you start building systems that handle thousands of concurrent operations, you realize that traditional threading models start to crack under pressure. Shared memory concurrency forces you into a world of mutexes, race conditions, and the constant fear that somewhere, somehow, two threads are fighting over the same piece of data. The cognitive overhead becomes overwhelming. You spend more time reasoning about locks th...")
08:3208:32, 18 November 2025 Top 50 Rust Interview Questions and Answers (2025 Edition) (hist | edit) [25,148 bytes] PC (talk | contribs) (Created page with "After reviewing hundreds of Rust interviews across startups and big tech, I’ve noticed a pattern: most interview guides focus on theory, but real interviews test your ability to think in Rust. This guide bridges that gap. 500px Whether you’re interviewing at a systems programming shop, a blockchain startup, or a web services company, these 50 questions cover what you’ll actually encounter. I’ve included not just answers, but...")
08:1308:13, 18 November 2025 Rust 1.90: The Speed Update — LLD Linker Makes Everything 7x Faster (hist | edit) [13,472 bytes] PC (talk | contribs) (Created page with "500px What if your Rust projects suddenly compiled 40% faster… without changing a single line of code? Released on September 18, 2025, Rust 1.90 brings one of the most impactful performance improvements in recent Rust history. By switching to the LLD linker as the default on Linux, this release dramatically cuts build times — especially for large projects and incremental rebuilds. Add workspace publishing support to Cargo, and you’ve got a r...")
07:5907:59, 18 November 2025 Rust Promised Fearless Concurrency. Erlang Shipped It in 1986. (hist | edit) [9,441 bytes] PC (talk | contribs) (Created page with "The Rust community celebrates fearless concurrency as a revolutionary achievement. Zero-cost abstractions, ownership semantics, and compile-time guarantees that prevent data races. It’s impressive engineering. But Erlang solved the same problems 39 years ago with a different approach that’s arguably more practical for distributed systems. 500px After spending years writing Rust for systems programming and recently diving deep into Erlang...")
07:5307:53, 18 November 2025 The Future of Systems Programming: Rust, Go, Zig, and Carbon Compared (hist | edit) [17,568 bytes] PC (talk | contribs) (Created page with "500px The systems programming landscape is undergoing its most dramatic shift since the transition from assembly to C. Four languages are vying to define the next two decades of infrastructure software: Rust with its memory safety revolution, Go with its simplicity-first philosophy, Zig with its zero-overhead obsession, and Carbon with its ambitious C++ migration story. After spending eight months benchmarking these languages across 23 rea...")
07:4707:47, 18 November 2025 Teaching Claude to Write Better Rust: Automating Microsoft’s Guidelines with Skills (hist | edit) [10,409 bytes] PC (talk | contribs) (Created page with "500px When Microsoft released their Pragmatic Rust Guidelines in September 2025, they did something clever. Beyond the typical human-readable documentation, they created a condensed, AI-optimized version specifically designed for coding assistants like Claude and GitHub Copilot. The timing couldn’t have been better, because just weeks later, Anthropic launched Claude Skills, a powerful new feature that lets you package expertise into reu...")
07:4307:43, 18 November 2025 10 Rust Design Patterns Every Developer Should Master in 2025 (hist | edit) [8,400 bytes] PC (talk | contribs) (Created page with "Rust forces you to think differently. The patterns that work in Java or Python often don’t translate. Here are the patterns that actually matter when writing Rust code. 500px 1. Newtype Pattern Wrap primitives to add type safety. Prevents mixing up values that happen to have the same type. <pre> struct UserId(i32); struct ProductId(i32); fn get_user(id: UserId) -> User { // can't accidentally pass ProductId here } let user_...")
05:1605:16, 18 November 2025 Zig’s Build System Is Quietly More Revolutionary Than Rust’s Borrow Checker (hist | edit) [7,708 bytes] PC (talk | contribs) (Created page with "It started, as these things often do, with a broken build. You know that feeling when the terminal mocks you with 47 red lines and one smug message — “missing dependency: please reinstall”? Yeah. That. We were migrating a small backend service — nothing fancy, just a caching layer — and I figured I’d try Zig. I’d heard people whispering about it like some underground cult of simplicity. “Zig’s build system is amazing,” they said. And honestly? I did...")
05:0905:09, 18 November 2025 We Built a Microkernel in Rust: Here’s What Actually Worked (hist | edit) [7,578 bytes] PC (talk | contribs) (Created page with "500px There’s this moment every systems developer has when they stare at their bootloader, watch a blank screen flash, and whisper: “Did I just write an OS… or a very expensive infinite loop?” That was us — three developers, one foolish dream: building a microkernel in Rust from scratch. No libc, no POSIX, no kernel to lean on. Just cargo, bare metal, and a questionable amount of caffeine. And the truth? Rust didn’t ma...")
05:0405:04, 18 November 2025 The 7 Rust Features That Make You a Better Programmer (hist | edit) [4,609 bytes] PC (talk | contribs) (Created page with "A focused tour of the language habits that force better design, fewer bugs, and faster delivery. 500px One compile-time rule saved a team from shipping a data-loss bug on a Friday night. That rule changed how the team designs libraries from that day forward. Rust will change how code is written and how problems are thought about. This article lists seven concrete Rust features that improve coding skill. Read each entry like a short...")
05:0005:00, 18 November 2025 10 Rust Design Patterns That Separate Amateurs from Pros in 2025 (hist | edit) [7,443 bytes] PC (talk | contribs) (Created page with "500px Rust has earned its reputation for safety, performance, and control. But mastering its syntax isn’t enough. The real test comes when you have to design maintainable, scalable systems without fighting the borrow checker or drowning in lifetime annotations. That’s where design patterns come in. A design pattern is a reusable structure that solves a common software design problem. In Rust, these patterns adapt to ownership, borrowing,...")
04:5104:51, 18 November 2025 Four Rust Crates That Quietly Make Your Life Better (hist | edit) [8,082 bytes] PC (talk | contribs) (Created page with "500px Every Rust developer knows about serde, tokio, and clap. These are the workhorses, the crates that appear in nearly every Cargo.toml file. But the ecosystem’s real depth reveals itself in those smaller, focused libraries that solve specific problems elegantly. You add them to a project, they do exactly what they promise, and suddenly you wonder how you ever worked without them. Let me tell you about four crates that fall into this...")
04:4704:47, 18 November 2025 Rust’s Seven Cardinal Sins (hist | edit) [15,859 bytes] PC (talk | contribs) (Created page with "500px The typical advice about Rust focuses on fighting the borrow checker or avoiding unwrap. After building distributed systems in Rust for years, I’ve found the real sins are more subtle. These are mistakes that experienced developers make after they’ve learned the basics, patterns that seem reasonable until they surface under production load as mysterious performance degradation or unexpected memory pressure. Sin #1: Fighting the Opt...")
04:4004:40, 18 November 2025 Building a Linux Kernel Module in Rust: Zero Panics in 14 Months Production (hist | edit) [17,758 bytes] PC (talk | contribs) (Created page with "Our custom network driver, written in C, was a disaster. It crashed production servers 3–4 times per week. Each crash required manual intervention, customer downtime, and post-mortem analysis. The bugs were always memory safety issues: use-after-free, null pointer dereferences, buffer overflows. We spent 18 months fighting these crashes. Then Linux 6.1 merged initial Rust support, and we decided to rewrite our driver in Rust. The team’s reaction: skeptical borderin...")
04:3104:31, 18 November 2025 Why We Bet on Rust to Supercharge Feature Store at Agoda (hist | edit) [12,475 bytes] PC (talk | contribs) (Created page with "Rust has become the language everyone seems to be talking about. From startups to tech giants, companies are rewriting core systems and touting dramatic gains in performance, reliability, and safety. With so much buzz, it’s easy to wonder if Rust is just the latest industry fad or if there’s real substance behind the hype. At Agoda, several teams had already begun experimenting with Rust for performance-critical workloads, and their positive experiences caught our a...")
04:1804:18, 18 November 2025 Nobody Warned Me About Rust’s IDE Support. Now I’m Warning You (hist | edit) [6,385 bytes] PC (talk | contribs) (Created page with "I’ve been writing Java and Go professionally for the past four years. Last month, I finally decided to dive deep into Rust. Everyone told me the borrow checker would be the hard part. They were wrong. The IDE tooling hit me first. 500px I’m still learning Rust, still working through ownership concepts, but the development experience itself has been the real adjustment. Here’s what I’m dealing with. Compile Times Are Not What I Exp...")
04:1304:13, 18 November 2025 The Rise of Embedded WebAssembly: Rust’s WASI Revolution (hist | edit) [6,842 bytes] PC (talk | contribs) (Created page with "500px There’s a silent revolution happening — and it’s not in browsers anymore. It’s happening inside routers, IoT boards, game consoles, and even satellites. That revolution is WebAssembly (Wasm) — powered not by JavaScript, but by Rust. And the secret weapon behind it? WASI — the WebAssembly System Interface. Wait, WASI? What’s That? When WebAssembly was first introduced, it was meant for browsers — to run...")
04:0804:08, 18 November 2025 Forget Futures — These 4 Async Patterns Made My Rust Code Cleaner and Faster (hist | edit) [10,857 bytes] PC (talk | contribs) (Created page with "500px Rust async can be practical without wrestling with combinator hell. The ideas here are simple. They scale. They made my code easier to reason about and 2–3x faster in real workloads. Read closely, try the snippets, and use what fits. Why this matters — short and sharp As systems grow, raw futures and nested combinators become a maintenance tax. The code compiles, but it is brittle. Bugs hide in corners. Latency appears in produc...")
04:0104:01, 18 November 2025 Remember: Don’t Mention Rust During Interviews (hist | edit) [10,956 bytes] PC (talk | contribs) (Created page with "500px Today I want to write something beyond tech. I want to talk about psychology and humanity in tech, about the unspoken social dynamics that often matter more than our technical skills. There’s an unwritten rule circulating among experienced developers: Don’t mention Rust in a non-Rust team during interviews. At first glance, this seems absurd. Why would discussing a modern, safe systems language be a problem? Yet from my experie...")

15:3915:39, 17 November 2025 5 Rust Concurrency Models (With Real Code Examples) (hist | edit) [10,756 bytes] PC (talk | contribs) (Created page with "This article shows five practical Rust concurrency models, working code, measured results, and hand-drawn-style diagrams so that a single read will change the way code is written from this moment onward. Read this if performance matters, if correctness matters, and if the next bug must be prevented rather than debugged at midnight. The examples are small, real, and reproducible. Follow the code, run it with --release, and compare results on your machine. file:Quick_o...")
15:3215:32, 17 November 2025 We stopped writing Rust. Rust started writing itself (hist | edit) [7,219 bytes] PC (talk | contribs) (Created page with "our codebase was smaller, cleaner, and somehow… faster. That’s when we realized: Rust’s meta-programming isn’t just about reducing boilerplate — it’s about unleashing performance that humans could never manually write. Welcome to the revolution where Rust writes the hard parts, and you just design the logic. 500px What Meta-Programming Really Means in Rust If you’ve written macros in C or templates in C++, you might thin...")
15:2715:27, 17 November 2025 Inside Rust’s Meta-Programming Revolution: Macros 2.0 (hist | edit) [10,494 bytes] PC (talk | contribs) (Created page with "500px “Wait, Rust Has Macros?” If you’re new to Rust, the word macro probably evokes flashbacks to C’s preprocessor nightmares — #define spaghetti, double-evaluated expressions, and impossible-to-debug expansions. But Rust’s macros are nothing like that. They’re not dumb text substitution engines.  They’re syntactic transformers — fully aware of types, scopes, and syntax trees. And with Macros 2.0, Rust is...")
15:2115:21, 17 November 2025 I Wrote 30,000 Lines of Rust, This Is What It Taught Me (hist | edit) [10,934 bytes] PC (talk | contribs) (Created page with "The first time Rust humbled me, my terminal looked like a Christmas tree. I had just threaded a reference through three layers of functions to shave allocations off a hot path. The compiler responded with a polite avalanche: cannot borrow foo as mutable because it is also borrowed as immutable. I’d spent years in languages where tests—or worse, production—find these edges. Rust found mine before the code ever ran. I was annoyed. Then I slept. In the morning, I r...")
15:1415:14, 17 November 2025 Why Zig Is Quietly Doing What Rust Couldn’t: Staying Simple (hist | edit) [6,450 bytes] PC (talk | contribs) (Created page with "The Hook The first time I wrote Zig code, I laughed out loud. Not because it was funny — but because I couldn’t believe something this… quiet still existed in modern programming. No macros yelling at me. No borrow checker existential crises. Just me, a function, and a compiler that didn’t feel like a disappointed parent. After years of wrestling Rust — the language that promised to save us all from C but somehow turned into a personality test — Zig felt li...")
15:0915:09, 17 November 2025 Kornia-rs: The Rust Library You Will End Up Using (Even If You Do Not Do AI) (hist | edit) [7,752 bytes] PC (talk | contribs) (Created page with "500px Image pipelines belong in safe, fast Rust now. Short sentences. Sharp stakes. This is not a tutorial about theory. This is a practical invitation. If the project on your desk must touch pixels, frames, or thumbnails, keep reading. Why this matters, in plain terms If images touch your stack, a tiny library can save days. Not in vague ways. In concrete ways: * Fewer bindings. Less glue code to maintain. * Fewer memory bugs. Rust enforc...")
15:0315:03, 17 November 2025 10 Rust Tricks Every Senior Engineer Knows (But Juniors Miss) (hist | edit) [9,734 bytes] PC (talk | contribs) (Created page with "500px This article is not a list of fanciful tricks. This is a field guide written for the engineer who already knows Rust basics and wants practical moves that produce measurable wins. Each trick contains a small, clear code example, a short benchmark summary, and a plain-English explanation of why the change matters. Read this with a cup of coffee and a code editor open. How to read this piece * Each trick follows: Problem → Change...")
14:5714:57, 17 November 2025 Rust’s New Borrow Checker (Polonius) Is Coming (hist | edit) [16,301 bytes] PC (talk | contribs) (Created page with "500px Rust has long been praised for combining performance and safety, but one of its most subtle — and at times frustrating — features is the borrow checker. It’s strict, quirky, sometimes surprising. Over the years, Rust’s community has pushed the boundaries of what the borrow checker accepts, culminating in non-lexical lifetimes (NLL). But there’s still more to do. Enter Polonius — a next-generation borrow checker (or, more p...")
14:5214:52, 17 November 2025 Generic Associated Types (GATs): The Rust Feature That Finally Solves Async Trait Hell (hist | edit) [7,782 bytes] PC (talk | contribs) (Created page with "500px When I first dipped my toes into async Rust, I hit the wall. You know the one — the dreaded “async trait methods are not supported” compiler error. It felt absurd. Rust could safely juggle references across threads, guarantee memory safety at compile time… but couldn’t let me write an async function inside a trait? What followed was months of hacky workarounds: async_trait macros, lifetimes from hell, boxing fu...")
14:4514:45, 17 November 2025 Why Rust Nearly Sank Our Startup API (And What Nobody Tells You Until It’s Too Late) (hist | edit) [9,522 bytes] PC (talk | contribs) (Created page with "500px I’m about to break a sacred rule in tech: never say anything bad about Rust in public. But someone needs to tell the other side, before more startups bet their runway on a language that’s not built for speed — human speed, not benchmark speed. This is the story of how we rebuilt our bank-grade API in Rust, why the decision haunts me, and the messy, painful truth you won’t find on Twitter threads or conference slides....")
14:4114:41, 17 November 2025 Why I’d Never Write a Web API in Rust (and What I’d Use Instead) (hist | edit) [7,148 bytes] PC (talk | contribs) (Created page with "500px Rust is powerful. Rust is fast. Rust is… not what you want for a web API. Let’s get one thing straight — I love Rust. I’ve tinkered with it for system-level work, and yes, it’s a piece of engineering art. But when someone says, “We’re building our next web API in Rust!” — I quietly take a sip of my coffee, nod politely, and prepare for the postmortem six months later. The Myth: “Rust Is Faster, So It...")
14:3614:36, 17 November 2025 Rust Vs Go: One Is A Scam — Prove Me Wrong (hist | edit) [5,590 bytes] PC (talk | contribs) (Created page with "500px I have shipped production systems in both, argued with teammates about both, and changed my mind more than once. This is the part most threads skip, written in plain words and grounded in real incidents. The Hook No One Likes To Admit Teams rarely pick Rust or Go only for speed. They pick a feeling. Go feels calm: quick to start, easy to hire, friendly standard library. Rust feels strict: slower at the start, fewer hidden traps later....")
14:3214:32, 17 November 2025 Go Just Killed Rust’s Only Advantage (And Nobody’s Talking About It) (hist | edit) [8,048 bytes] PC (talk | contribs) (Created page with "I’ve been scrolling through Medium and tech Twitter for months now, constantly bumping into the same heated debates: Rust versus Go. As someone who’s been writing Go professionally for over a year, I kept seeing Rust enthusiasts talking about memory safety like it was the holy grail. Eventually, curiosity got the better of me. I decided to dig deep and figure out what Rust actually offers that Go doesn’t. 500px What I found surpri...")
14:2714:27, 17 November 2025 Electron Is Over: Rust GPUI Just Ended Cross-Platform Compromise (hist | edit) [7,058 bytes] PC (talk | contribs) (Created page with "500px For years we told ourselves a story: ship once, run everywhere, and accept the weight that comes with it. We accepted slow first paint. We accepted memory spikes. We accepted that a browser would live inside every window we launched. The convenience felt worth the cost — until it didn’t. In the last year, the bar moved. Rust GPUI — originally built inside a modern, high-performance code editor — changed how desktop apps feel u...")
14:2514:25, 17 November 2025 I Rewrote A Java Microservice In Rust And Lost My Job (hist | edit) [8,407 bytes] PC (talk | contribs) (Created page with "500px A dark comedy about choosing the “wrong” technology. On Monday I had a badge. On Tuesday my badge was a coaster. The crime? I rewrote “Billing-Quotes,” a sleepy Java microservice with thirteen upstreams, in Rust. p95 got leaner. CPU chilled. Memory dropped. The infra bill blinked smaller numbers like a hotel minibar. And then the CTO told me to bring a box. This is the autopsy of a decision that was technically...")

18 November 2025

17 November 2025