New pages

19:0519:05, 23 November 2025 Slices (hist | edit) [9,686 bytes] PC (talk | contribs) (Created page with "Yesterday we checked out Loops in-depth and other niceties around them, if you missed it, I’d recommend checking it out below. Loops Loops in programming (fundamental and very useful), including Rust, are like a repeating task you tell the computer to… medium.com In this post, let’s discuss Slices, it’s day 19 here we go! A slice in Rust is like a window into a portion of a sequence, such as an array, vector, or string. It’s a reference to a contiguous chunk...")
19:0219:02, 23 November 2025 Designing Domain-Specific Languages (DSLs) with Rust Macros and Parser Combinators (hist | edit) [20,389 bytes] PC (talk | contribs) (Created page with "500px Domain-Specific Languages represent one of the most powerful tools in a developer’s arsenal for creating expressive, maintainable solutions to complex problems. When combined with Rust’s sophisticated macro system and type-safe parser combinators, DSLs become not just powerful but also reliable and performant. This exploration delves into the techniques and strategies for crafting both embedded and external DSLs that leverage Rust...")
18:5918:59, 23 November 2025 Loops (hist | edit) [10,421 bytes] PC (talk | contribs) (Created page with "Loops in programming (fundamental and very useful), including Rust, are like a repeating task you tell the computer to do until a certain condition is met or a task is finished. Think of loops as asking someone to keep stirring a pot of soup until it’s ready. Yesterday we covered iterators, and if you missed that you can check it out below. Iterators After playing with vectors, and enums the last two days, it’s time to look in on Rust’s iterators -a feature that ma...")
18:5618:56, 23 November 2025 Beyond WebAssembly: Where Rust is Quietly Dominating (and You Haven’t Noticed) (hist | edit) [10,380 bytes] PC (talk | contribs) (Created page with "When you hear “Rust,” your mind might immediately jump to WebAssembly (Wasm). And for good reason! Rust’s unparalleled performance, memory safety, and small binary sizes make it an ideal choice for compiling to Wasm, enabling high-performance code to run in browsers and beyond. It’s a fantastic pairing that has rightly garnered massive attention in the web development community. 500px But to only see Rust through the lens of WebA...")
18:5418:54, 23 November 2025 Easy Concurrency Mastery: Exploring the Read-Write Lock Pattern in Rust for Performance (hist | edit) [9,995 bytes] PC (talk | contribs) (Created page with "500px Photo by Pixabay: https://www.pexels.com/photo/gray-metal-typewriter-part-in-close-up-photo-261626/ In another article we discussed the Lock pattern. In this article we used the type. The problem with this type is, is that it doesn’t distinguish between reading from a resource, like accessing an element in a vector, and writing to it. In cases where many threads need to read a resource at one, and there are a few write-o...")
18:5118:51, 23 November 2025 Iterators (hist | edit) [7,254 bytes] PC (talk | contribs) (Created page with "After playing with vectors, and enums the last two days, it’s time to look in on Rust’s iterators -a feature that makes working with collections feel like a breeze. Iterators are like a conveyor belt in a factory, delivering items one by one for your code to process, without you needing to micromanage the details. They’re flexible, efficient, and pack a punch for real-world tasks. In this guide, we’ll walk through what iterators are, how to use them, and how the...")
18:4818:48, 23 November 2025 Vectors (hist | edit) [8,158 bytes] PC (talk | contribs) (Created page with "After getting cozy with enums and pattern matching in our previous days, it’s time to turn our attention to another Rust superstar: vectors. If you missed yesterday’s writeup, you can check out the link below. Pattern Matching with Enums Yesterday, we looked into Rust enums, seeing how they can be used for modelling choices, states, and even data-packed… medium.com If enums are about choosing between distinct options, vectors are about gathering a bunch of items...")
18:4318:43, 23 November 2025 Unlocking Effortless Asynchrony: Mastering the Easy Event-Driven Paradigm in Rust (hist | edit) [10,305 bytes] PC (talk | contribs) (Created page with "500px Photo by Tima Miroshnichenko: https://www.pexels.com/photo/alarm-clocks-on-wooden-shelves-8327954/ Introduction Sometimes, when your program has a task that takes a lot of time, like working with databases, web services, or complex calculations, you might want to let it happen in the background. This way, your program can keep running smoothly without waiting for the time-consuming task to finish. In Rust, we can ac...")
18:3218:32, 23 November 2025 The Story of the Rust Foundation (hist | edit) [2,892 bytes] PC (talk | contribs) (Created page with "500px Image: Rust Foundation logo (credits: Rust Foundation) Hello, Rustaceans We’re already halfway through the month. Keep that momentum rolling. In this issue, we’ll discuss how Rust Foundation came to be, present you a Rust challenge, spotlight an amazing Rust project, and share 10 incredible links of the week. Here’s issue 89 for you! MAIN NEWS The Story of the Rust Foundation Ever wondered how the Rust Foun...")
18:2718:27, 23 November 2025 The Cloudflare Outage and Rust’s Marketing Problem (hist | edit) [4,271 bytes] PC (talk | contribs) (Created page with "500px On November 18, 2025, a huge chunk of the internet went dark. Services like X, ChatGPT, Canva, and Letterboxd all went offline. The root cause? A single unwrap() call in Rust code that triggered a panic across Cloudflare’s 330+ datacenters. The fallout was immediate: some defended Rust’s safety guarantees, others claimed this proved Rust isn’t special, and many were simply confused about what had gone wr...")
18:2418:24, 23 November 2025 Rust Won’t Save Your Go Service — Fix Postgres And Move 8% Instead (hist | edit) [8,983 bytes] PC (talk | contribs) (Created page with "500px Our Go checkout service wasn’t on fire. That would have been easier. Instead, it was slowly cooking: * Dashboards getting a little redder every month * Support tickets creeping up * Latency graphs that looked “tolerable” if you squinted Inside the team, the conversation went exactly the way you’d expect in 2022: “Go is hitting its limit, we should rewrite the core in Rust.” “Rewrites are dangerou...")
18:2118:21, 23 November 2025 Why I Replaced Parts of My Python Automation Stack With Rust Extensions (hist | edit) [6,223 bytes] PC (talk | contribs) (Created page with "500px When Python Hit Its Limits I’ve been building automation frameworks in Python for years — orchestrating APIs, running micro-agents, moving data, and managing workflow pipelines. Python is elegant, easy to maintain, and fast enough for most tasks. But eventually, the bottlenecks became obvious: * Heavy numeric computation in data preprocessing * Tight loops in internal ETL engines * High-frequency API polli...")
18:1718:17, 23 November 2025 This Week in Rust 626: Android’s Rust Revolution & Format Macro Magic (hist | edit) [13,704 bytes] PC (talk | contribs) (Created page with "Hey Rustaceans! Welcome back to another edition of This Week in Rust. This week brings some of the most compelling real-world validation of Rust’s value proposition yet — with Google Android revealing game-changing metrics on Rust’s impact, plus significant compiler improvements that make everyday Rust development smoother. From a 1000x reduction in memory safety vulnerabilities to revolutionary format macro optimizations, let’s dive into what’s making waves th...")
18:1418:14, 23 November 2025 Rust Crate : I Forked a 220k-Download Wi-Fi Scanner and Removed All CLI Dependencies (hist | edit) [8,227 bytes] PC (talk | contribs) (Created page with "500px Summary: I forked the popular Rust crate wifiscanner and rewired it to use native system interfaces on Windows, macOS, and Linux—no more brittle parsing of netsh, iw, or airport. The result is a new crate, wifi_scan, that’s faster, more reliable, i18n-friendly, and future-proof. It’s on GitHub and crates.io—feedback and PRs (especially for macOS) are very welcome. Why I did this The original wifiscanner has ov...")
18:1318:13, 23 November 2025 Rust Kernel Abstractions: How Linux Drivers Got Memory-Safe Without Runtime Overhead (hist | edit) [10,982 bytes] PC (talk | contribs) (Created page with "500px he compiler kept rejecting my interrupt handler. I was convinced Rust was too strict for kernel work. Then I realized my entire approach was wrong — I was trying to share mutable state across interrupt contexts without synchronization. Rust’s borrow checker enforces exclusive mutable access or shared immutable access at compile time, preventing data races that cause kernel panics. The borrow checker wasn’t being pedantic...")
18:0818:08, 23 November 2025 Async Trait Bounds in Rust: Send + Sync Demystified (hist | edit) [9,288 bytes] PC (talk | contribs) (Created page with "500px The compiler throws an error. Something about Send not being satisfied. You add + Send to your trait bound. Now it complains about Sync. You add that too. It compiles. You have no idea why. Here’s what nobody mentions upfront: async trait bounds aren’t about being correct. They’re about being honest with the compiler about what your code might do across threads. You’re not alone in this confusion. A 2025 survey...")
18:0618:06, 23 November 2025 Tokio Made My Rust Service 10x Faster — Then It Made My Life 10x Harder (hist | edit) [8,340 bytes] PC (talk | contribs) (Created page with "The night Tokio almost broke me started with a beautiful graph. 500px Requests per second were up. p95 latency was down. The dashboard said we had never been faster. My phone said something else. Support was flooded with complaints about timeouts while every metric smiled at us. That was the moment I learned that making a Rust service ten times faster is easy. Living with that speed is the hard part. When Tokio Fel...")
18:0418:04, 23 November 2025 Rust Won The Benchmarks, Go Won The Jobs: What I Learned The Hard Way (hist | edit) [6,937 bytes] PC (talk | contribs) (Created page with "500px Photo by Greg Jewett on Unsplash I went through a phase where my identity as an engineer was basically a language logo. If you asked me “Rust or Go?”, I would not just answer. I would defend Rust with passion. Memory safety. Zero-cost abstractions. Fearless concurrency. Meanwhile my Go friends would laugh and say, “Cool, but our services are in production.” One day I opened my Medium stats, my GitHub, my inbox...")
18:0218:02, 23 November 2025 Rust’s Borrow Checker Isn’t Out to Get You — It’s Saving You From Yourself (hist | edit) [8,110 bytes] PC (talk | contribs) (Created page with "500px (and how to fix those maddening E0499 / E0502 / E0506 errors with clean patterns) If you’ve ever danced with Rust’s borrow checker and felt your feet get tangled, you’re not alone. The code below looks innocent enough: <pre> fn main(){ let mut cur = &mut 7; let mut nxt: &mut i32 = &mut *cur; if true { let y = &mut *cur; // E0499: cannot borrow `*cur` as mutable more than once // *cur = 7;...")
17:5917:59, 23 November 2025 From C to Rust: Lifetimes — Compile-Time Garbage Collection (hist | edit) [9,542 bytes] PC (talk | contribs) (Created page with "Note: This post builds on concepts from From C to Rust: ownership. If you haven’t read that yet, start there to understand Rust’s ownership system, which forms the foundation for lifetimes. 500px In the previous post on ownership, we saw how Rust prevents use-after-free and double-free bugs by tracking which variable owns each heap allocation. The owner is responsible for cleanup, borrowers can temporarily access the data, an...")
17:4917:49, 23 November 2025 The Future is Containerless: Why Rust and WASM are Coming for Docker (hist | edit) [8,070 bytes] PC (talk | contribs) (Created page with "500px Okay, let’s have a talk. For what feels like forever, Linux containers have been the cool kids on the block. If you were doing anything in the cloud, you were using Docker. It was the law. And honestly? It was amazing for a while. Docker and Kubernetes completely changed the game, and we all jumped on board. But I’ve got this nagging feeling lately, and I don’t think I’m alone. The magic is starting to fade. Wh...")
17:4717:47, 23 November 2025 RustFrom Rapid Scripts to Blazing Speed: Mastering Python and Rust Together (hist | edit) [9,124 bytes] PC (talk | contribs) (Created page with "500px You know that feeling, right? You’re in the zone, hammering out some Python code. It feels amazing. You can build a script, an API, or mess with a huge dataset in what feels like no time at all. Python is just… easy. It’s friendly, it makes sense, and there’s a library for basically anything you can dream up. But then you hit it. The wall. 🧱 Your script starts to drag its feet. It’s processing data so slowly you co...")
17:4517:45, 23 November 2025 Go Devs, Meet Your New Memory MVP: Why Rust’s Ownership Model is a Game-Changer! (hist | edit) [17,972 bytes] PC (talk | contribs) (Created page with "500px Alright, folks, listen up! Ever sit there, sipping your coffee, and wonder if you could actually have it all when it comes to writing code? I mean, fast and safe? For a long time, many of us, especially in the Go community (and, hey, I’m right there with you!), have really loved how Go’s garbage collector, or GC, just handles memory for us. It makes concurrency feel pretty chill and, honestly, frees up our brains...")
17:4017:40, 23 November 2025 Resource consumption by Rust (hist | edit) [8,302 bytes] PC (talk | contribs) (Created page with "500px You run `cargo build` on a large Rust codebase, something like compiling a blockchain node from source and saw your system freeze or face an out-of-memory error. I faced this issue when building Mina Protocol’s rust node on my 16GB machine and got me thinking what is happening in my machine during Rust compilation and can it be optimized for a successful build? This happens due to compiled languages like Rust can ask...")
17:3817:38, 23 November 2025 Automating GitHub Weekly Labels: My New Rust Tool (hist | edit) [5,487 bytes] PC (talk | contribs) (Created page with "If you’ve ever spent time managing GitHub repositories, you know that labels can make or break your workflow. They help organize issues, track progress, and make project dashboards readable at a glance. But let’s be honest: manually creating labels for every repository in an organization — especially weekly labels — can quickly become tedious. That’s why I decided to automate the process. 500px Enter my latest side...")
17:3617:36, 23 November 2025 When Rust Won’t Vectorize: How to See Why, Prove Whose Fault It Is (rustc vs LLVM), and Fix It (x86 and AArch64) (hist | edit) [11,646 bytes] PC (talk | contribs) (Created page with "500px You’ve got a hot loop that blazes on x86_64 but stubbornly refuses to vectorize on aarch64. You peek at LLVM IR, you squint at Godbolt, you try a few tweaks…and still no SIMD on Apple M-series or modern ARM servers. Let’s solve this properly: * What’s happening? Your loop shape asks for gathers from src + an in-place RMW store to latents. x86 can often paper over this with AVX2 gathers and tolerant alias analys...")
17:3317:33, 23 November 2025 We Didn’t Rewrite the Java Monolith — We Parked a Rust Sidecar Next to It (hist | edit) [9,466 bytes] PC (talk | contribs) (Created page with "500px Photo by Trevor Vannoy on Unsplash The first time someone suggested Rust at work, it sounded like this: “We should just rewrite the whole service in Rust. Java is clearly the bottleneck.” Our on-call charts were ugly: * p95 around the “token generation” API was spiking during traffic bursts * JVM CPU looked bad * GC logs were full of minor collections It was easy to blame Java. But when we dug in,...")
17:3017:30, 23 November 2025 Rust Reshapes Blockchain Development as Performance Demands Soar (hist | edit) [45,219 bytes] PC (talk | contribs) (Created page with "500px Rust has emerged as the defining language for next-generation blockchain infrastructure, powering platforms that process billions of daily transactions while attracting more new developers than Ethereum for the first time in 2024. The ecosystem now commands $22 billion in total value locked, processes over 200 million transactions daily, and employs 4 million developers globally — double the number from just two years ag...")
17:2717:27, 23 November 2025 Building Robust Unit Tests for btcturk websocket Client: A Testing Journey in Rust (hist | edit) [5,681 bytes] PC (talk | contribs) (Created page with "This is basically a follow up story of my learning journey, which is some how not written by AI (very un common these days) A couple years ago, while I was refreshing my knowledge about rust I studied the most about unit tests. 500px Rust for Startest (Part-3 Tests) I was studying Rust as always and improving my library here about websockets… medium.com Coming to end of 2025, I finally released a nice package, wh...")
17:2417:24, 23 November 2025 Rust + Web3 + AI: Fully Automated On-Chain Intelligence Agents (hist | edit) [14,355 bytes] PC (talk | contribs) (Created page with "500px Fast, safe, async, predictable. We will be creating a continuous stream of AI-generated blockchain insights. It combines Rust, Web3 infrastructure, and LLM-powered reasoning to form a fully autonomous intelligence agent. The agent will be capable of monitoring Ethereum in real time, interpreting on-chain dynamics, generating human-readable analysis, and publishing it to the world. SYSTEM STRUCTURE The system listens to new blocks as...")
17:2117:21, 23 November 2025 Comprehensive Guide to Using Rust in Android Development (hist | edit) [17,882 bytes] PC (talk | contribs) (Created page with "Introduction 500px If you’ve been keeping an eye on modern systems programming, you’ve probably noticed Rust popping up everywhere — and Android development is no exception. Rust brings memory safety, strong performance, and a fresh way of thinking about low-level code. In this guide, I’ll walk you through how Rust fits into Android projects, why teams are adopting it for performance-critical...")
17:1617:16, 23 November 2025 Rust String Concatenation: A Friendly, No-Nonsense Guide (with Optimal Patterns) (hist | edit) [7,133 bytes] PC (talk | contribs) (Created page with "500px Rust gives you two main string flavors: &str (a borrowed string slice) and String (an owned, heap-allocated, growable string). Concatenation is really just about where the bytes live and who owns them. Below is an engaging, practical tour through the most common combinations — plus a simple decision chart so you can pick the optimal approach for your use case. Quick Primer: &str vs String * &str — a view in...")
17:1317:13, 23 November 2025 Rust Lifetimes Without the Confusion: A Practical Guide (hist | edit) [7,538 bytes] PC (talk | contribs) (Created page with "500px Rust lifetimes aren’t arcane syntax they’re the guardrails that prove your references are safe before your code ever runs. You’re three hours into a refactor and everything compiles. Clean. You add one line, just borrowing a string reference, and the compiler explodes with expected named lifetime parameter. Four lines of angry red text with apostrophes and angle brackets you've never typed before. You stare at it. You google it...")
17:0817:08, 23 November 2025 Rust vs TypeScript on Solana: Building a High-Throughput Pump.fun On-Chain Indexer (Modular, Scalable, 429-Safe) (hist | edit) [5,894 bytes] PC (talk | contribs) (Created page with "500px Introduction Solana’s high-throughput architecture makes it a fantastic chain for real-time applications, but it also forces you to design your systems around speed, concurrency, and resilience. Over the past few weeks, I built a Pump.fun on-chain listener in both Rust and TypeScript — not for trading, but to understand how Solana log events work, how to build a clean indexing pipeline, and how to design extensib...")
13:1213:12, 23 November 2025 A Minimal Rust Template for Advent of Code (hist | edit) [6,145 bytes] PC (talk | contribs) (Created page with "Every year when Advent of Code begins, I find myself repeating the same routine: copy last year’s folder, delete the old solutions, reset the inputs, and re-establish the structure. It technically works, but it’s tedious, and it makes the first day of AoC feel messier than it should. I’ve used several Rust templates over the years, but most of them fell into two extremes: either too bare-bones to stay organized for the entire AoC days, or too elaborate, with traits...")
13:0713:07, 23 November 2025 7 Rust Patterns That Outperform C++ (hist | edit) [7,193 bytes] PC (talk | contribs) (Created page with "500px Learn 7 Rust patterns that outperform C++ in high-performance systems, from memory safety to zero-cost abstractions and fearless concurrency. Why Rust vs. C++ Is More Than Just Hype For decades, C++ was the gold standard for high-performance systems programming. From operating systems to game engines, it offered speed, control, and flexibility unmatched by higher-level languages. But then came Rust. At first, i...")
13:0613:06, 23 November 2025 How to (Safely) Create a Global, Mutable Singleton in Rust — and When You Actually Should (hist | edit) [8,432 bytes] PC (talk | contribs) (Created page with "500px Summary * Prefer no globals: construct early (e.g., in main) and pass &mut/& where needed. * If you must have a global: use std::sync::LazyLock (Rust ≥ 1.80) with a lock type (Mutex/RwLock) that matches your access pattern. * For single-threaded graphics loops (typical OpenGL): consider thread_local! + RefCell to avoid cross-thread locking. * For counters/flags: use atomics. * Avoid static mut and ra...")
13:0313:03, 23 November 2025 Ubuntu’s Rust Transition and the sudo-rs Security Vulnerabilities: A Technical Analysis (hist | edit) [4,677 bytes] PC (talk | contribs) (Created page with "Ubuntu’s effort to modernize its system stack by rewriting critical components in Rust has been one of the most significant architectural changes in recent years. As part of this transition, Canonical introduced sudo-rs, a Rust-based reimplementation of the traditional sudo command. While the goal is to enhance safety and long-term maintainability, recent security issues in sudo-rs show that such transitions are not without challenges. This article dives into the te...")
13:0213:02, 23 November 2025 RustError: Why does Clippy warn about op ref for - and *, not just ==? (And how to fix it cleanly) (hist | edit) [7,448 bytes] PC (talk | contribs) (Created page with "500px If you’ve ever overloaded operators in Rust, you’ve probably written a little “forwarding impl” to avoid duplicating logic. Something like: <pre> impl Sub<&ComplexCommutativeOperator> for &RealCommutativeOperator { type Output = ComplexCommutativePolynomial; fn sub(self, rhs: &ComplexCommutativeOperator) -> ComplexCommutativePolynomial { // real logic lives here →...: } } impl Sub<Complex...")
13:0013:00, 23 November 2025 Rust Is Quietly Transforming Android Security — And the Entire Software Industry Should Pay Attention (hist | edit) [14,961 bytes] PC (talk | contribs) (Created page with "500px How Google drove memory-safety bugs below 20% for the first time — and why Rust’s impact goes far beyond security. Google’s adoption of Rust in Android has reduced memory-safety vulnerabilities by over 1000x compared to C/C++. Memory-safety bugs now represent less than 20% of Android’s vulnerabilities for the first time in the platform’s history. Even more surprising: Rust is not only safer — it is...")
12:5812:58, 23 November 2025 Rust’s ? Operator: Little Mark, Big Ergonomics (hist | edit) [7,762 bytes] PC (talk | contribs) (Created page with "500px You’re reading some Rust code and stumble on: let mut file = File::create("foo.txt")?; What’s that lone question mark doing there — and why does every idiomatic Rust project seem to love it? Short answer: ? is Rust’s error propagation operator. It says, “If this call succeeds, give me the value. If it fails, return the error from the current function—possibly converting it—right now.” No exceptions, no hid...")
12:5512:55, 23 November 2025 Why Rust Is Loved But Not (Yet) Everywhere at Work — and How to Change That (hist | edit) [10,105 bytes] PC (talk | contribs) (Created page with "500px Summary: Rust really is “loved,” and it’s proving itself in serious production systems. But love doesn’t pay migration costs, retrain whole teams, or plug smoothly into incumbent toolchains. Big orgs adopt risk policies, not languages. The path forward is targeted, measured, adjacent adoption: pick memory-critical components, interop intentionally, invest in training and governance, and instrument the business outcome...")
12:5312:53, 23 November 2025 Making it Easy to Use OpenAPI in Your Rust Projects (hist | edit) [12,653 bytes] PC (talk | contribs) (Created page with "Rust has stood out as a high-performance and secure language. Obviously, this is not limited to low-level development; thanks to its rich ecosystem of crates, Rust is also a great alternative for web development. However, one problem remains: the productivity of the average developer in Rust is usually not as high as in other languages. Knowing this, the Rust community has been working hard to create tools that improve this experience. One of these tools is the Utoipa...")
12:5012:50, 23 November 2025 How rustup Manages Multiple Toolchains (Behind the Shims) (hist | edit) [8,136 bytes] PC (talk | contribs) (Created page with "500px There are two kinds of Rust developers: * The ones who think rustup is “just a version manager.” * The ones who dug deeper and realized rustup is a tiny engineering miracle disguised as a CLI tool. If you’re in group #1, this article will change that forever. rustup is the invisible backbone of the Rust ecosystem. It’s the reason: * You can switch between stable, beta, nightly * You can cross-compile to A...")

17:3217:32, 22 November 2025 Using Rust, Google’s Real Test: Memory Vulnerability Rate on Android Is 1000× Lower Than C/C++! (hist | edit) [10,703 bytes] PC (talk | contribs) (Created page with "In recent years, Rust has become a somewhat controversial language. On one hand, the U.S. government agencies publicly call for moving away from C/C++ and transitioning to memory-safe languages like Rust. Large tech companies are also embracing Rust, emphasizing that it leads to safer code. On the other hand, many developers have developed a clear “anti-hype” sentiment — feeling Rust is over-praised and significantly harder to learn than most languages. Amid this...")
17:2217:22, 22 November 2025 Declarative vs Procedural Macros: How Rust Keeps Metaprogramming Safe (hist | edit) [8,569 bytes] PC (talk | contribs) (Created page with "500px There’s a moment every Rust developer goes through: you write the same boilerplate struct implementations for the tenth time and think, “There must be a better way.” That’s where macros come in — Rust’s answer to code generation. But unlike C++ templates or Python metaclasses, Rust’s macros are safe, structured, and visible. And that’s not an accident. It’s one of the most carefully engineered p...")
17:1817:18, 22 November 2025 Rust’s Next Superpower: Pattern Types That Kill Useless Runtime Checks (hist | edit) [18,797 bytes] PC (talk | contribs) (Created page with "500px One job had crashed. One slice had been empty when it was not supposed to be. One small assumption had slipped through everything. Nothing exotic. No unsafe. No complex lifetime trick.  Just a function that took a slice, grabbed the first element, and trusted the caller. Everyone on the team “knew” that slice was never empty. Someone even wrote it in a comment. The type system did not know that. So one day, under...")
17:1317:13, 22 November 2025 Patching AMSI in Memory with Rust A Red Teamer’s Guide (hist | edit) [7,011 bytes] PC (talk | contribs) (Created page with "500px Hey everyone! Maverick here. I’m a red team enthusiast who recently decided to level-up my Rust game. Over the next few months I’ll be rewriting a bunch of classic offensive techniques in Rust, both to practice the language and to have cleaner, faster tools in my kit. Today we’re looking at one of the most classic Windows living-off-the-land tricks: bypassing AMSI (Antimalware Scan Interface) by directly patching AmsiS...")
17:0917:09, 22 November 2025 The Day Our Go Goroutines Blew Up Memory and Rust Did Not (hist | edit) [6,369 bytes] PC (talk | contribs) (Created page with "Our production server died in under three minutes. 500px No graceful degradation. No slow crawl. Just a wall of alerts, a frozen dashboard, and 32GB of RAM gone. The autopsy report was brutal: 47,000 goroutines, all alive, all hungry, all waiting on I/O. That was the night I learned that concurrency is not about how cheaply you can spawn work. It is about how fast you can slam into the limits of the machine if you do not put g...")
17:0617:06, 22 November 2025 I Used Python for Everything — Until I Discovered Rust (2) (hist | edit) [7,660 bytes] PC (talk | contribs) (Created page with "500px Photo by Dima Pechurin on Unsplash For most of my career, Python wasn’t just a tool — it was the tool. APIs? Python. Automation? Python. Data scripts, CLI tools, web services, quick prototypes? Python, Python, Python. And honestly, it worked. Python was friendly. Python was fast to write. Python made me feel productive. So when I first picked up Rust, it was out of boredom more than necessity. A weekend curiosi...")

23 November 2025

22 November 2025