New pages

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...")
14:2214:22, 17 November 2025 I Fought the Rust Borrow Checker for 3 Months. Here’s How I Finally Won (hist | edit) [9,009 bytes] PC (talk | contribs) (Created page with "500px For the first three months of learning Rust, I was in a state of constant, low-grade fury. I’m not new to this. I’ve built production systems in Python, Java, and Go. I know what a pointer is. I know what a reference is. I know how to manage memory. Or so I thought. My first 90 days with Rust were not a “learning curve.” They were a war. A war against an enemy that was pedantic, all-seeing, and infuriatingl...")
10:5610:56, 17 November 2025 Rust GPUI vs Electron: Startup, Memory, and the UX Gap That Matters (hist | edit) [4,345 bytes] PC (talk | contribs) (Created page with "500px That was the moment I realised something was broken in my stack, not in my code. The feature was small and the release was routine. The angry screenshot from a user was not. Electron had carried me for years.  Then one day my desktop app started feeling like a badly disguised browser tab that refused to close. That was the day I started to take Rust based GPUI seriously. When Electron stopped feeling reasonable I loved Ele...")
10:5110:51, 17 November 2025 Rust vs DPDK: The Unexpected Showdown Changing How Packets Really Fly (hist | edit) [5,590 bytes] PC (talk | contribs) (Created page with "500px You know those moments when two legends walk into the same room, and you just know someone’s leaving with a bruised ego? Yeah, that’s how I felt watching Rust and DPDK square off in the high-speed packet I/O arena. Let’s be honest: packet I/O isn’t exactly the sexiest topic in tech. It’s like plumbing — you only care when it’s broken and flooding your datacenter. But the Rust vs DPDK debate? Oh, that’s pure enginee...")
10:4610:46, 17 November 2025 How Rust Solves Kernel Data Races (hist | edit) [8,838 bytes] PC (talk | contribs) (Created page with " 200 px I crashed a production server. Thread A reads device driver state, thread B writes to it — undefined behavior doesn’t warn you, it just waits for the perfect moment to detonate. We had locking in place, but someone missed one critical section during a refactor six months back. Code review didn’t catch it. Testing didn’t catch it. The race window was microseconds wide, only triggered under specific load. Customer’...")
10:3410:34, 17 November 2025 Decoding the Future: Why Developers Are Choosing Rust GPUI Over Electron for Blazing-Fast Desktop UI (hist | edit) [10,565 bytes] PC (talk | contribs) (Created page with " file:Electron,_Weighed_down_by_the_past.webp You know that feeling, right? 😫 You click to open a desktop app- maybe it’s your chat client, or a productivity tool- and for a second, nothing. Then, your laptop fan kicks in, sounding like it’s about to take off, all for something that feels kinda basic. Ugh. We’ve all been there, trust me. For ages, the whole “write once, run anywhere” dream for desktop apps usually came with a sneaky, annoying price ta...")
09:0009:00, 17 November 2025 Rust Error : How do I convert from an integer to a string ? (hist | edit) [9,306 bytes] PC (talk | contribs) (Created page with "File:Rust Error How do I convert from an integer to a string.jpg The short answer: use .to_string() (or format!) Here’s the modern, idiomatic way to convert an integer into a String in Rust: fn main() { let x: u32 = 10; let s: String = x.to_string(); println!("{}", s); } That’s it. * x is a u32. * .to_string() converts it into an owned String. * println! happily prints it. If you prefer a formatting macro: let x: u32 = 10; let s = for...")
08:3408:34, 17 November 2025 How to Print the Type of a Variable in Rust (The Practical, Zero-Crate Way) (hist | edit) [5,125 bytes] PC (talk | contribs) (Created page with "“What type is this?” is one of those questions you ask a dozen times a day while learning or debugging Rust. Good news: you don’t need nightly features or extra crates to peek at a value’s type — the standard library already has your back. Summary Use the functions in std::any: use std::any::{type_name, type_name_of_val}; fn main() { let mut my_number = 32.90; // defaults to f64 println!("{}", type_name_of_val(&my_number)); // prints "f64" // Alte...")
08:2108:21, 17 November 2025 Why Rust Is the Fastest Growing Programming Language in 2025 (hist | edit) [10,632 bytes] PC (talk | contribs) (Created page with "The numbers don’t lie — Rust’s developer community has doubled in two years, and major tech companies are betting their future on it. When the White House publishes a cybersecurity report recommending a programming language over industry standards like C and C++, you pay attention. That happened in February 2024, when the US government officially endorsed Rust for memory safety reasons. But this wasn’t just political theater. It reflected a seismic shift already...")
08:2008:20, 17 November 2025 A Powerful Example of Macros and Traits in Rust (hist | edit) [12,450 bytes] PC (talk | contribs) (Created page with "When writing integration tests for the Rust web APIs of the Flutter-Actix app and ReallyStick, I discovered that SQLx’s #[sqlx::test] macro not only simplified my code but also solved a disk space problem. More importantly, I learned a valuable lesson: always read the crate documentation instead of blindly following tutorials. But beyond that, #[sqlx::test] is a perfect example of how Rust’s macro system and trait system work together to create powerful abstr...")
08:1808:18, 17 November 2025 Conditional Compilation in Rust with Feature Flags (hist | edit) [6,798 bytes] PC (talk | contribs) (Created page with "I was checking out the OpenObserve — an open-source observability tool which you can self-host or use their cloud offering which offers free, standard and enterprise tier to choose from. Written completely in rust so I thought of checking the codebase on Github to get myself more aquatinted with rust language. While doing so I found a #[cfg(feature = “enterprise”)] being used in many places. Looking at it, one can tell that any function or block decorated wi...")
08:1508:15, 17 November 2025 Breaking Rust Isn’t the Future of Music — You Are (hist | edit) [3,871 bytes] PC (talk | contribs) (Created page with "The Mirage of a #1 Hit A cowboy with a gravelly voice, a windswept hat, and 2.2 million monthly Spotify listeners just topped a Billboard chart. Except he never lived, never breathed, never broke his heart, and definitely never held a guitar. He is an AI-generated mirage named Breaking Rust. And yet — he became a global headline. But the real story isn’t that AI made a hit. It’s that we wanted to believe it did. The Manufactured Panic When the news broke that...")
08:1408:14, 17 November 2025 Rust Is Cool. But Java Just Did Something Smarter in 2025 (hist | edit) [3,834 bytes] PC (talk | contribs) (Created page with "In July 2025, I watched a viral X thread: “Rust is eating Java’s lunch — memory safety, speed, no GC.” I felt the FOMO. My team was knee-deep in a high-frequency trading system — 2 million TPS, sub-millisecond latency. Rust looked tempting. Then Java 25 dropped Project Leyden. One config change later, our JVM startup went from 8.2 seconds to 180 milliseconds. No rewrite. No retraining. Just smarter Java. By November 2025, that single upgrade saved us $42,00...")
08:1108:11, 17 November 2025 Rust’s Loop: How One Game Changed Development Forever (hist | edit) [10,419 bytes] PC (talk | contribs) (Created page with "Rust’s update-driven model created a profitable loop between developers and content creators — but it’s making every game feel the same. The survival game Rust didn’t just create a genre — it created a business model. Through consistent monthly updates, a symbiotic relationship with content creators, and a profitable DLC strategy, Facepunch Studios demonstrated that finished games never need to be truly finished. The result has been revolutionary, transformat...")
08:1008:10, 17 November 2025 How Rust Manages Memory Like a Pro without needing a Garbage Collector? (hist | edit) [10,141 bytes] PC (talk | contribs) (Created page with "Rust is ruling the programming world. People are loving the language; almost every other article recommended to me is the performance benchmark of Rust v/s Other languages and how Rust is saving thousands of dollars in server cost due to the performance benefits brought by Rust. Rust is at the top of almost every StackOverflow Developer Survey. Rust is yet again the most admired programming language (72%), followed by Gleam (70%), Elixir (66%) and Zig (64%). Gleam is...")
08:0708:07, 17 November 2025 Listing Files in a Directory in Rust (The Practical Guide, with Python Parallels) (hist | edit) [6,856 bytes] PC (talk | contribs) (Created page with "If you’re coming from Python, you’ve probably written this a hundred times: import os files = os.listdir("./") It’s compact, readable, and “just works.” In Rust, you have the same power with a little more type safety and control. This post shows several idiomatic ways to list directory contents in Rust — from a quick printout to filtered, sorted, recursive, globbed, and even async listings. Copy–paste ready. Summary: The One-Liner Version Rust’s stand...")
08:0408:04, 17 November 2025 When the Optimizer Lies: The Subtle Art of Unsafe Performance in Rust (hist | edit) [6,556 bytes] PC (talk | contribs) (Created page with "If you’ve ever gone down the “I can make this faster” rabbit hole in Rust, you know the feeling: you sprinkle in some unsafe, tighten your loops, and suddenly — boom — a benchmark shows a 2× improvement. You lean back, satisfied. Then you rerun it on another machine… and it’s slower. Or worse — it segfaults. Welcome to the shadowy world of Rust’s optimizer — where your code and LLVM’s assumptions sometimes part ways. And sometimes, the optimi...")
08:0308:03, 17 November 2025 5 Async Patterns That Made My Rust Code 3x Faster (hist | edit) [9,107 bytes] PC (talk | contribs) (Created page with "I didn’t expect a single missing await to slow down an entire service. But that’s how Rust teaches you: with silence, then pain, then clarity. Async in Rust is not magic. It’s a contract: structure your concurrency well, and it rewards you with speed. Break that contract, and your service stutters, stalls, or quietly blocks the whole executor. Press enter or click to view image in full size Avoid holding locks across await points Locking in async Rust is s...")
07:5907:59, 17 November 2025 Building AI & Machine Learning Apps with Rust (hist | edit) [27,126 bytes] PC (talk | contribs) (Created page with "From ChatBots to Neural Networks — Making AI Fast and Safe! 🤖✨ Python dominates AI/ML, but Rust is catching up fast! If you want to build AI applications that are blazing fast, memory-efficient, and production-ready, Rust is your secret weapon. Whether you’re building chatbots, recommendation systems, or running neural networks, let’s explore how Rust makes AI development exciting! 🚀 🤔 Why Use Rust for AI/ML? The AI Challenge: * 🐌 Python is slow...")
07:5607:56, 17 November 2025 THE JOURNEY TO BECOMING A WORLD-CLASS RUSTACEAN-1 (hist | edit) [9,152 bytes] PC (talk | contribs) (Created page with "I went the route of ignoring Rust, while being vocal about the EVM being sufficient, and even got into fiery arguments regarding EVM vs SVM and CosmWasm. Despite the inherent flaws the Ethereum Virtual Machine possesses, I believe — and still do — that a system built specifically for an ecosystem will remain the top platform in the long run, the platform of choice for any tangible protocol built in the space. Given how intensely I defended the EVM and Solidity, its p...")
07:5307:53, 17 November 2025 I Re-wrote One Spring Boot Microservice in Rust and Measured Everything for 30 Days (hist | edit) [3,882 bytes] PC (talk | contribs) (Created page with "1. Why I even considered mutiny against Spring Boot I’ve shipped Spring Boot code since 2.0. I like the ergonomics, I like @Transactional, and I really like the ecosystem. But at 03:14 on Black Friday our user-auth service cold-started in 14.2 s on a t3.medium. The ELB threw 502s for 38 seconds. We lost ~4 k sign-ups. Post-mortem showed the JVM was 180 MB at idle and the container image cracked 420 MB. I asked myself: “Is the JVM the only culprit, or can a c...")
07:5207:52, 17 November 2025 My Python Comfort Zone Shattered: Embracing Rust for Blazing-Fast, Bug-Free Code (hist | edit) [14,669 bytes] PC (talk | contribs) (Created page with "You know that feeling, don’t you? That cozy, familiar hum you get from a tool that just fits? For the longest time, honestly, that was Python for me. It was my trusty sidekick, my go-to for pretty much everything. I’m talking about those quick little scripts I’d whip up before my first coffee, all the way to massive web apps and super intricate data pipelines. Seriously, if there was a job that needed doing, Python was usually the very first language that popped...")
07:4907:49, 17 November 2025 Bare-Metal Rust: Safety Below the OS (hist | edit) [13,110 bytes] PC (talk | contribs) (Created page with "I spent six hours fighting the borrow checker over an interrupt handler. Six hours. The compiler kept rejecting my code, insisting I couldn’t share mutable state between the main loop and the ISR. I was convinced Rust was being pedantic about something that worked fine in C for decades. When I finally compiled a workaround using unsafe, I stress-tested it. Race condition at 847 interrupts per second. The borrow checker had been right. The bug would’ve shipped. In C,...")
07:4807:48, 17 November 2025 Rust HashMap Interactions Made Simple: The Entry API (hist | edit) [13,742 bytes] PC (talk | contribs) (Created page with "Rust’s entry API is something that isn’t often talked about, but it makes maps easier to use without risking panics, and it helps eliminate redundant lookups. If you’ve ever written code like if map.contains_key(k) { … } else { … }, then you’ve been doing two lookups when one would do, and adding another layer of nesting. The entry API solves those problems and provides an idiomatic and safe alternative to working with maps. In this article I’m going to...")
07:4707:47, 17 November 2025 Rust’s Tokio vs. Go’s M:N Scheduler: A Deep Dive into Async I/O Thread Contention (hist | edit) [6,313 bytes] PC (talk | contribs) (Created page with "We added more workers to the Tokio pool expecting faster throughput. Instead, tail latencies doubled and CPU utilization dropped. The problem wasn’t the scheduler or our code logic — it was the runtime and OS kernel competing for the same file descriptors during parallel async I/O. Understanding how Tokio’s work-stealing differs from Go’s cooperative M:N model explains why identical workloads can show wildly different contention patterns. How Tokio’s Work-Stea...")
07:4407:44, 17 November 2025 Rust vs DPDK: I Rewrote Our Network Stack and the Borrow Checker Won (hist | edit) [10,075 bytes] PC (talk | contribs) (Created page with "I spent six hours fighting the borrow checker on a Tuesday night. My packet parser kept failing with lifetime errors I couldn’t understand. The compiler rejected every fix. I was convinced Rust was being pedantic about something that didn’t matter. Then I stress-tested my original C implementation — segfault at 12 million packets per second. The borrow checker hadn’t been pedantic. It had been right. Why I Even Attempted This Migration Our team was running a DPDK...")
07:4207:42, 17 November 2025 Introducing flutter tantivy: Bringing Rust-Powered Full-Text Search to Flutter (hist | edit) [6,486 bytes] PC (talk | contribs) (Created page with "Search is everywhere. From finding the right email in your inbox to discovering products in an e-commerce app, full-text search has become an essential feature in modern applications. But implementing high-performance search on mobile devices? That’s a different challenge altogether. Today, I’m excited to share flutter_tantivy — a Flutter plugin that brings the blazing-fast Tantivy search engine, written in Rust, directly to your Flutter applications. The Proble...")
07:4007:40, 17 November 2025 Rust Macros Tutorial That Stops the Boilerplate (hist | edit) [8,937 bytes] PC (talk | contribs) (Created page with "The struct definition spreads across 80 lines. Field by field, you type the same pattern: name, type, a derive attribute, a builder method, a validation check. Copy, paste, adjust. The code works but maintaining it feels like punishment. Change one field and suddenly you’re updating six different places, hoping you caught them all. We write boilerplate because we have to, but nobody actually enjoys maintaining code that’s 70% identical patterns with tiny variations....")
07:3807:38, 17 November 2025 Rust in Space: Why NASA Trusts It for Mission-Critical Flight Software (hist | edit) [15,369 bytes] PC (talk | contribs) (Created page with "The telemetry buffer crashed after 47 hours of continuous testing. Three threads racing to write sensor data — textbook race condition. In C, this would’ve reached Mars before we found it. Rust caught it at compile time. I wasn’t expecting that. I’d rewritten the module specifically to test Rust’s safety claims, half-expecting the hype to fall apart under real spacecraft constraints. Instead, the compiler pointed at line 47 and said “you’re trying to mutabl...")
07:3407:34, 17 November 2025 Why This Python Dev Switched to Rust (and What I Gained!) (hist | edit) [14,959 bytes] PC (talk | contribs) (Created page with "You know that feeling, right? That moment when you finally find the one? The programming language that just gets you, speaking your coding love language, you know? For the longest, longest time, that was absolutely Python for me. It was my trusty sidekick, my go-to for pretty much everything-from those super quick little scripts you bash out before breakfast, all the way to huge, sprawling web apps. I even used it for my sneaky automation tools and, like, anything wit...")
07:3307:33, 17 November 2025 Why One in Six Go Developers Are Switching to Rust in 2025 — And What It Means for Your Career (hist | edit) [7,941 bytes] PC (talk | contribs) (Created page with "Why teams are trading garbage collectors for guard rails — and how to stay valuable either way. A lot of Go teams love their speed — until unsafety, tail-latency, or infra cost knocks. In 2025, more of them are reaching for Rust not as a fad, but as a seatbelt. If your stack speaks Go today, your career plan should speak Rust tomorrow. The Pattern You’re Seeing (and Why It Feels Sudden) A payments platform replaces a hot Go path with a Rust crate, and the p95...")

08:2308:23, 16 November 2025 How Rust Guarantees Memory Safety (and Why You Rarely See Segfaults) (hist | edit) [9,496 bytes] PC (talk | contribs) (Created page with "If you’re eyeing Rust because it’s “fast like C++ but safe like Java,” you’re not alone. The two big promises that draw people in are memory safety and no segmentation faults in safe code. What’s surprising is how Rust achieves this: not with a garbage collector or a runtime nanny, but with a few powerful compile-time rules. Here’s the short version: Summary: Rust prevents entire classes of memory bugs at compile time with an ownership system and...")
08:2008:20, 16 November 2025 Rust’s Firmware Revolution: How Memory Safety Stopped Our $2M Hardware Recall (hist | edit) [14,883 bytes] PC (talk | contribs) (Created page with "The email arrived, Production line down. Two hundred server boards refusing POST. I pulled up the logs from our test lab, still half-asleep, expecting the usual suspects — bad solder joints, maybe a silicon stepping issue with the new CPU batch. Instead, I found something worse. Our BIOS update from the previous week had a bug in the memory initialization code. Classic buffer overflow during RAM timing calibration. The overflow corrupted ACPI tables. Those tables told...")
08:1608:16, 16 November 2025 An idea for a GPU programming language feature: polysemous function type checking — Rust (hist | edit) [30,271 bytes] PC (talk | contribs) (Created page with "In languages like Rust with powerful type systems, developers are able to encode a lot about their program’s behavior in the type system. This makes it possible to validate a large number of your program’s assumptions at compile time, which is very favorable for a number of reasons. My experience with GPU programming has been that this is harder to achieve. A primary reason for this is that GPU programming is SIMT (Single Instruction, Multiple Threads), meaning that...")
08:1308:13, 16 November 2025 What Does Rust Use Instead of a Garbage Collector? (hist | edit) [7,937 bytes] PC (talk | contribs) (Created page with "Summary: Rust frees memory deterministically using ownership + RAII (drop on scope exit). The compiler proves who owns what, inserts “drop glue” to run destructors at the right time, and forbids use-after-free. No background GC thread, no tracing pauses. When you opt in, you can also use reference counting (Rc/Arc)—which is GC-like in spirit but explicit, local, and non-tracing. The mental model: Ownership, not collection Rust doesn’t periodically “...")
08:1208:12, 16 November 2025 Rust Won’t Kill C++ — But Here’s the Real Threat Nobody’s Talking About (hist | edit) [5,667 bytes] PC (talk | contribs) (Created page with "Every time a new programming language pops up, someone dramatically declares: “THIS is the end of C++!” Meanwhile, C++ is sitting in a rocking chair, sipping a bit of malloc() tea, whispering, “I’ve survived Java, Python, Go, and even JavaScript. Nice try, kid.” Rust, though — Rust felt different. It showed up wearing a leather jacket, talking about “safety” and “ownership,” and everyone started swooning. Devs whispered, “Finally! A systems lang...")
08:0908:09, 16 November 2025 Rust’s Borrow Error : Why You Can’t Store a Value and a Reference to It in the Same Struct (hist | edit) [14,061 bytes] PC (talk | contribs) (Created page with "You write what feels like perfectly reasonable Rust: struct Thing { count: u32, } struct Combined<'a>(Thing, &'a u32); fn make_combined<'a>() -> Combined<'a> { let thing = Thing { count: 42 }; Combined(thing, &thing.count) } …and the compiler very kindly replies: error: cannot return value referencing local variable 'thing' error: 'thing' does not live long enough You stare at it. But the struct owns the Thing. The reference is to a field inside that...")
08:0708:07, 16 November 2025 5 Concurrency Mistakes in Go, Rust, and Node That Kill Throughput (hist | edit) [4,303 bytes] PC (talk | contribs) (Created page with "Your app is not slow because of your database. It is slow because your threads, goroutines, and event loops are fighting each other for air. Every engineer hits this wall once. The system “works,” but throughput drops as soon as real traffic hits. You scale horizontally. You blame latency. But deep down, you know something else is bleeding CPU cycles quietly. 1. Shared State Without Boundaries The deadliest concurrency bug is invisible — shared state mutation....")
08:0508:05, 16 November 2025 Building a Rust Compiler: Understanding the Magic Behind the Curtain (hist | edit) [10,422 bytes] PC (talk | contribs) (Created page with "The terminal cursor blinks. You type cargo build and press enter. Lines of text scroll past—dependencies resolving, crates compiling, optimizations running. Two minutes later, a binary appears. Executable. Ready to run. You trust this process completely without understanding any of it. You’re not alone in that blind spot. A 2024 developer survey found that 71% of programmers have never looked at compiler internals, even though they interact with compilers dozens o...")
08:0308:03, 16 November 2025 How to Completely Uninstall Rust (installed via rustup) — The Friendly, No-Gotchas Guide (hist | edit) [5,806 bytes] PC (talk | contribs) (Created page with "So you installed Rust on Ubuntu with the classic one-liner: curl https://sh.rustup.rs -sSf | sh …and now you want it gone, cleanly. Maybe you’re freeing space, switching machines, or just doing a fresh setup. Whatever the reason, here’s a crisp, battle-tested way to remove rustup, rustc, cargo, toolchains, and caches — without leaving PATH gremlins behind. Summary (Optimal Fast Path) If you installed Rust using rustup (the curl script above), run: # 1) U...")
08:0108:01, 16 November 2025 Rust Error : “lifetime may not live long enough” — why &static fn(T) - T doesn’t mean what you think (hist | edit) [6,039 bytes] PC (talk | contribs) (Created page with "You’ve got a tidy little generic: pub struct Test<T> { f: &'static fn(T) -> T, } …and Rust fires back: the parameter type T may not live long enough help: consider adding a bound T: 'static Why is the lifetime of a reference to a function pointer tangled up with the lifetime of T? After all, code lives forever, right? Let’s unpack what the compiler is protecting you from, and then fix it in a few idiomatic ways. The core intuition * &'static fn(T)...")

17 November 2025

16 November 2025