Jump to content

Main public logs

Combined display of all available logs of JOHNWICK. You can narrow down the view by selecting a log type, the username (case-sensitive), or the affected page (also case-sensitive).

Logs
(newest | oldest) View ( | ) (20 | 50 | 100 | 250 | 500)
  • 07:49, 17 November 2025 PC talk contribs created page Bare-Metal Rust: Safety Below the OS (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:48, 17 November 2025 PC talk contribs created page Rust HashMap Interactions Made Simple: The Entry API (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:47, 17 November 2025 PC talk contribs created page Rust’s Tokio vs. Go’s M:N Scheduler: A Deep Dive into Async I/O Thread Contention (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:44, 17 November 2025 PC talk contribs created page Rust vs DPDK: I Rewrote Our Network Stack and the Borrow Checker Won (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:42, 17 November 2025 PC talk contribs created page Introducing flutter tantivy: Bringing Rust-Powered Full-Text Search to Flutter (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:40, 17 November 2025 PC talk contribs created page Rust Macros Tutorial That Stops the Boilerplate (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:38, 17 November 2025 PC talk contribs created page Rust in Space: Why NASA Trusts It for Mission-Critical Flight Software (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:34, 17 November 2025 PC talk contribs created page Why This Python Dev Switched to Rust (and What I Gained!) (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:33, 17 November 2025 PC talk contribs created page Why One in Six Go Developers Are Switching to Rust in 2025 — And What It Means for Your Career (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:23, 16 November 2025 PC talk contribs created page How Rust Guarantees Memory Safety (and Why You Rarely See Segfaults) (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:20, 16 November 2025 PC talk contribs created page Rust’s Firmware Revolution: How Memory Safety Stopped Our $2M Hardware Recall (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:16, 16 November 2025 PC talk contribs created page An idea for a GPU programming language feature: polysemous function type checking — Rust (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:13, 16 November 2025 PC talk contribs created page What Does Rust Use Instead of a Garbage Collector? (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:12, 16 November 2025 PC talk contribs created page Rust Won’t Kill C++ — But Here’s the Real Threat Nobody’s Talking About (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:09, 16 November 2025 PC talk contribs created page Rust’s Borrow Error : Why You Can’t Store a Value and a Reference to It in the Same Struct (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:07, 16 November 2025 PC talk contribs created page 5 Concurrency Mistakes in Go, Rust, and Node That Kill Throughput (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:05, 16 November 2025 PC talk contribs created page Building a Rust Compiler: Understanding the Magic Behind the Curtain (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:03, 16 November 2025 PC talk contribs created page How to Completely Uninstall Rust (installed via rustup) — The Friendly, No-Gotchas Guide (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:01, 16 November 2025 PC talk contribs created page Rust Error : “lifetime may not live long enough” — why &static fn(T) - T doesn’t mean what you think (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)...")
  • 07:59, 16 November 2025 PC talk contribs created page If StackOverflow Had Feelings, It Would Be Written in Rust (Created page with "If StackOverflow were a person, it would be that relentlessly helpful friend who corrects your grammar and your runtime errors. You show up at 3 a.m., eyes glazed, whispering “segfault,” and they slide over a mug of coffee and a page of code comments. They’re blunt, a little pedantic, but they keep you from setting your production hair on fire. Now imagine that friend was a programming language. That language is Rust. It’s StackOverflow’s vibe distilled into...")
  • 07:56, 16 November 2025 PC talk contribs created page Why Google, Microsoft, and the White House Chose Rust? (Created page with "The Language Nobody Expected to Win Something strange happened in the programming world. A systems language — one designed for low-level, nerdy work — became the darling of startups, cloud companies, and even governments. That language is Rust. And if you haven’t paid attention yet, the gap between you and the opportunity is closing fast. In 2010, Mozilla was stuck. They had a browser filled with C and C++, and those languages had a problem. Memory safety vulner...")
  • 07:54, 16 November 2025 PC talk contribs created page Bridging Two Worlds: Integrating Rust with Go Using CGo (Created page with "Combining Rust’s Safety with Go’s Simplicity ⚡ Have you ever wondered how to leverage Rust’s blazing-fast performance and memory safety in your Go applications? The answer lies in CGo, Go’s powerful foreign function interface. In this guide, we’ll explore how to seamlessly integrate Rust code into your Go projects, combining the best of both worlds! 🚀 🤔 Why Integrate Rust with Go? Before diving into the technical details, let’s understand why this...")
  • 07:52, 16 November 2025 PC talk contribs created page Binary Diet: Shrinking Rust Releases Without Sorcery (Created page with "“It’s just printing text,” he said. Fair point. A C version would’ve been what, 20KB? I muttered something about static linking and moved on. But that number kept bugging me. Four megabytes for twelve lines of code felt wrong. The Thing Nobody Tells You Here’s what happened: I built with cargo build --release and assumed that meant "optimized." Turns out, Rust's idea of optimized means "fast to execute" not "small to ship." The default release profile optimiz...")
  • 07:50, 16 November 2025 PC talk contribs created page I Built My Own AI Girlfriend in Rust — And She Actually Remembers Me (Created page with "Why I chose privacy over convenience, and how you can build your own AI companion that never forgets 🤔 The Problem That Started It All Let’s be honest — we’ve all tried ChatGPT, Claude, or other AI assistants. They’re impressive, sure, but there’s something fundamentally broken about the experience. Every conversation starts from scratch. They don’t remember that you told them your name yesterday, your favorite programming language, or that inside joke...")
  • 07:48, 16 November 2025 PC talk contribs created page Profiling Rust Made Easy: cargo-flamegraph, perf & Instruments (Created page with "Think of your Rust program like a busy playground. Some kids (functions) are calmly swinging; others are hogging the slide. Profiling is how you watch the playground to learn where time is really being spent — so you can fix the bottlenecks instead of guessing. Below is a practical guide that borrows the best tips from the Rust community forum, a hands‑on blog tutorial, and a short case study showing how one team cut CPU usage by ~70% after reading a flamegraph t...")
  • 07:46, 16 November 2025 PC talk contribs created page Rust — 7 Essential Crate That Will Instantly Elevate Your Project in Rust (Created page with "In Rust development, choosing the right third-party libraries (Crate) can significantly improve project quality and development efficiency. This article introduces 7 Crates that can greatly enhance Rust projects in key areas like error handling, serialization, asynchronous programming, HTTP requests, parallel computation, logging, and database access. Each Crate is paired with practical code examples and performance comparison data to help you quickly understand its valu...")
  • 07:44, 16 November 2025 PC talk contribs created page Meet Puhu: A Fast Python Image Library (with a Secret Rust Core) (Created page with "Let me start with “Why I built Puhu?” If you’re a Python developer who has ever worked with images, you’ve probably used Pillow. It’s the reliable, go-to library for tasks such as resizing profile pictures and generating thumbnails. Pillow is legendary, but it’s also over two decades old. In the tech world, that’s ancient. As a Python developer who was starting to learn Rust, I found myself staring at Pillow and thinking… “I wonder if I can make that ...")
  • 07:42, 16 November 2025 PC talk contribs created page Rust in the Backend: When (and When Not) to Replace Your Node/Python Services (Created page with "Rust in the Backend: When (and When Not) to Replace Your Node/Python Services The Significance of Rust in Backend Development As the landscape of backend development continues to evolve, Rust emerges as a compelling alternative to traditional programming languages like Node.js and Python. Its unique combination of performance, safety, and concurrency makes it an attractive option for developers looking to build robust and efficient server-side applications. Why Cons...")
  • 07:41, 16 November 2025 PC talk contribs created page Fixing Rust’s “linker cc not found” on Debian (WSL on Windows 10): A Clear, No-Nonsense Guide (Created page with "You’ve installed Rust on Debian inside Windows Subsystem for Linux (WSL), ran your first rustc or cargo build, and—boom—got hit with: error: linker `cc` not found Good news: nothing’s wrong with Rust. You’re just missing the system C toolchain that Rust uses to link your final binary. On Linux, Rust typically invokes a system linker via a driver called cc (usually provided by GCC). On a fresh Debian/WSL install, that toolchain often isn’t there yet. Th...")
  • 07:40, 16 November 2025 PC talk contribs created page Rust Data Structures: Vec T, & T , Box T. Do You Really Understand Collection Containers? (Created page with "Now that we have encountered more and more data structures, I have organized the main data structures in Rust from the dimensions of primitive types, container types, and system-related types. You can count how many you have mastered. As you can see, containers occupy half of the data structure landscape. When mentioning containers, you may first think of arrays and lists — containers that can be iterated. But in fact, as long as some specific data is wrapped inside...")
  • 07:35, 16 November 2025 PC talk contribs created page Finally Understanding Rust Ownership: A Visual Guide (Created page with "You’re staring at your screen. The code looks completely normal. You’ve written this exact pattern in three other languages this week. But the Rust compiler is throwing “value borrowed here after move” and you’re just… stuck. It’s not that you don’t understand the words. It’s that the ground rules changed and nobody mentioned it. Variables don’t work the way they used to. Memory feels suddenly fragile, like you’re handling something that might break...")
  • 07:33, 16 November 2025 PC talk contribs created page Rust’s “cannot move out of borrowed content” (a.k.a. “behind a shared reference”) — what it really means and how to fix it without (Created page with " Ever hit this? error[E0507]: cannot move out of `*line` which is behind a shared reference …and then you slap a .clone() on it, the code compiles, you ship it—and you’re still not sure why it failed in the first place? Let’s demystify this error, understand exactly what’s going on, and then walk through the most idiomatic, zero-allocation fixes. We’ll use your example and expand it into a general mental model you can reuse anywhere. The setup You ha...")
  • 07:31, 16 November 2025 PC talk contribs created page 7 Hard Security Wins Rust Guarantees — And 9 Traps It Won’t Save You From (Created page with "Pull Quote #1: Rust deletes memory-unsafe classes of bugs; Rust does not delete misuse. Rust’s pitch is paradoxical and powerful. Safe Rust makes entire categories of memory corruption impossible, yet exploitable systems still ship when logic, concurrency, or supply-chain decisions are wrong. 
That tension is the real story.
Not language wars. Risk accounting. Below is a precise map: what safe Rust kills outright, what Rust narrows, and what you must still def...")
  • 07:30, 16 November 2025 PC talk contribs created page Is it possible to cause a memory leak in Rust? (Created page with "Short answer: yes. Rust guarantees memory safety, not “no leaks ever.” It’s entirely possible — sometimes even desirable — to leak memory on purpose. The important bit is understanding how leaks happen in Rust, why they don’t violate memory safety, and how to avoid them when you don’t want them. This post walks through the most common leak patterns — Rc cycles, std::mem::forget, Box::leak, and Box::into_raw—and shows how to design your type...")
  • 07:28, 16 November 2025 PC talk contribs created page Inside the Borrow Checker: How Rust Validates Lifetimes in MIR (Created page with "Introduction: The Unsung Hero of Safety If Rust had a soul, it would be the borrow checker. Every time your code compiles successfully, it means this invisible guardian has run thousands of tiny logical proofs — verifying that your data isn’t being accessed after it’s dead, ensuring no two mutable borrows overlap, and making sure your program won’t corrupt memory like a wild C pointer. But here’s the fun part: The borrow checker doesn’t operate on your sour...")
  • 07:27, 16 November 2025 PC talk contribs created page How to Get a Slice as an Array in Rust (Without Losing Your Mind) (Created page with "You have an array or slice in Rust.
You know it definitely has (at least) three elements.
You want a nice, clean [u8; 3] out of it. So you try this: fn pop(barry: &[u8]) -> [u8; 3] { barry[0..3] // expected array `[u8; 3]`, found slice `[u8]` } …and the compiler gently tells you: expected array [u8; 3], found slice [u8] What’s going on, and how do you fix it in a clean, idiomatic way? Let’s walk through it step by step. Slices vs Arrays: Why the Co...")
  • 07:25, 16 November 2025 PC talk contribs created page How Miri Simulates Rust’s Memory Model for Undefined Behavior Detection (Created page with "Introduction — The Debugger That Thinks Like the Compiler Rust doesn’t let you “wing it” with memory. It’s strict, almost annoyingly so — but for good reason. You might have heard of Miri, the mysterious tool that catches undefined behavior before your program ever runs natively. But what is Miri, really?
It’s not a debugger. It’s not a linter. It’s something deeper — a virtual interpreter for Rust’s mid-level intermediate representation (MIR)...")
  • 07:24, 16 November 2025 PC talk contribs created page What If Rust Ran in the Browser Natively — Without WebAssembly? (Created page with "Introduction — The Thought Experiment No One Asked For, but We’re Doing Anyway We live in a world where Rust is already inside your browser — indirectly. Every time you load a WebAssembly module, Rust is running after being translated into a safe, sandboxed bytecode. It’s powerful, but it’s not native.
Rust doesn’t speak directly to the browser.
There is no rustc → Chrome, no rustc → Firefox engine, no “native Rust VM” running inside the Java...")
  • 01:02, 16 November 2025 PC talk contribs created page What Is the Equivalent of the join Operator Over a Vec String in Rust? (Created page with "If you’re coming to Rust from languages like Python, JavaScript, or Ruby, one of the first “quality of life” things you look for is a join operation: * Python: "-".join(["Foo", "Bar"]) * JavaScript: ["Foo", "Bar"].join("-") * Ruby: ["Foo", "Bar"].join("-") So naturally you ask: “What’s the equivalent of join for a Vec<String> in Rust?” You Google a bit, maybe see something about connect, maybe run into traits, lifetimes, and &str vs String,...")
  • 01:01, 16 November 2025 PC talk contribs created page Futures and Wakers Explained — The Real Async Engine Inside Rust (Created page with "When I first learned async programming in Rust, I made a rookie mistake.
I thought async and await worked like in JavaScript — just yield, resume, done. Oh, how wrong I was. Rust’s async system is nothing like JS, Python, or Go. It has no built-in runtime, no threads magically waiting around — it’s pure state-machine wizardry. Underneath every .await, there’s an engine of Futures and Wakers quietly scheduling, polling, and waking your code — all...")
  • 00:59, 16 November 2025 PC talk contribs created page Google Launches Magika 1.0: Rust-Powered AI Engine Doubles File Type Detection Capabilities (Created page with "Google has officially launched Magika 1.0, a production-ready AI model designed for precise file type identification. This release marks a significant advancement in automated content detection, particularly for cybersecurity applications. Announced this month, the milestone version features a core engine completely rewritten in the Rust programming language, resulting in substantial performance improvements. The system now supports over 200 distinct file formats, doubl...")
  • 00:58, 16 November 2025 PC talk contribs created page Rust-cargo-docs-rag-mcp (Created page with "they say necessity is the mother of invention. github.com/promptexecution/rust-cargo-docs-rag is an mcp server that downloads rust docs, counts the tokens, provides pagination and structures the information in a way that b00t can access it. I forked this because the original MCP server was so bad .. I noticed other people have also made rust doc servers; and google has picked those up but my version is better because it is dynamic (it allows the agent to request a sp...")
  • 00:57, 16 November 2025 PC talk contribs created page What Learning Rust Taught Me About My Java Code (Created page with "I didn’t switch teams.
I switched mental models. Rust didn’t make me abandon the JVM.
It made me delete a lot of Java habits that quietly cost latency, memory, and sleep. The punchline: ownership, explicitness, and resource discipline translate beautifully into modern Java (records, pattern matching, structured concurrency). And when they do, your “enterprise defaults” suddenly look… noisy. Pull Quote #1: “Rust didn’t replace Java for me; it replaced...")
  • 00:56, 16 November 2025 PC talk contribs created page 7 Boring Rust Sidecar Wins — Cut Memory 40% Without Rewrites (Created page with "A contrarian playbook for teams who prefer graphs over glory. We had the rewrite itch. You know the one.
“Throw it all away, do it ‘right’ in Rust, bask in p99 bliss.” We didn’t. We shipped a Rust sidecar instead — one tight, hot-path service next to our app — and cut memory by 40%, trimmed p95, and lowered GC churn. No heroics. No year-long migration. Just a smaller heap and quieter dashboards. The thesis: full rewrites are strategy claims disguised...")
  • 00:53, 16 November 2025 PC talk contribs created page Rust is King, But Java’s Project Loom Just Changed the Game (Created page with "So, for what feels like, I don’t know, forever in our super fast-paced software world, Rust has really been the go-to champion. Especially if you’re talking about things like system-level programming, apps where every millisecond counts, or, dare I say it, “fearless concurrency.” Developers, myself included, have totally gravitated towards it. Why? Because it promises stuff like memory safety without a garbage collector — which is, like, a huge deal — plu...")
  • 00:52, 16 November 2025 PC talk contribs created page Rust, ORT, ONNX: Real-Time YOLO on a Live Webcam- Part 3 (Created page with "In this third part of the series, we implement the actual YOLO object detector. As a reminder, the system runs across four threads: * the camera thread reads raw frames and hands them to thread 2; * the preprocessing thread resizes frames to 640×640 and bundles them with the original image and metadata into a YoloFrame; * the YOLO detector thread (this part) runs inference and draws results; * the UI thread renders the annotated output. Below is the YOLO...")
  • 00:51, 16 November 2025 PC talk contribs created page Learning Rust Part 2 — Data Layout and Enums in Practice (Created page with "The Learning Journey Continues! Let’s keep building our intuition for Rust’s memory model — and level up our tiny CLI app while we’re at it. Recap Last time, we learned ownership: every value in Rust has exactly one owner, and when the owner goes out of scope, the value is dropped. We saw moves, copies, borrows, and how those ideas make memory safety the language’s responsibility rather than yours. Today we’ll go one level deeper — into how data live...")
  • 00:49, 16 November 2025 PC talk contribs created page Building a High-Performance Orderbook Aggregator in Rust (Created page with "In the fast-paced world of cryptocurrency trading, having access to accurate and consolidated orderbook data is crucial for making informed trading decisions. In this article, we will explore the architecture and implementation of a high-performance orderbook aggregator built in Rust. This system fetches, processes, and merges orderbook data from multiple cryptocurrency exchanges, providing a unified view of the market. Architecture Overview The orderbook aggregator foll...")
  • 00:48, 16 November 2025 PC talk contribs created page The Pin API Explained: Why Rust’s Async Needs This Complexity (Created page with "I was two days into debugging a custom Future implementation when the compiler hit me with cannot be unpinned. I stared at that error for a solid thirty minutes. What did "unpinned" even mean? The future worked fine when I .awaited it directly, but the moment I tried storing it in a struct and polling it myself, everything exploded. Turns out I’d been thinking about async Rust completely wrong. The Problem Nobody Told Me About Here’s what broke: I wanted to wrap...")
  • 00:45, 16 November 2025 PC talk contribs created page The White-Collar Rust Belt (Created page with "A good name for the phenomenon is the White-Collar Rust Belt, which, humbly, is a name I made up. I’m referring to the vast quantity of vacant office space in the tall office buildings that you see clustered in big office parks and lining the sides of freeways. When the sun glimmers off their paneled windows, they look like impressive shining monuments to the so-called service economy. You’d think the buildings are chock-full of people sitting at their desks, working...")
(newest | oldest) View ( | ) (20 | 50 | 100 | 250 | 500)