Jump to content

User contributions for PC

Results for PC talk block log uploads logs
A user with 1,712 edits. Account created on 12 November 2025.
Search for contributionsExpandCollapse
⧼contribs-top⧽
⧼contribs-date⧽
(newest | oldest) View ( | ) (20 | 50 | 100 | 250 | 500)

17 November 2025

16 November 2025

  • 08:2308:23, 16 November 2025 diff hist +9,496 N 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..." current
  • 08:2208:22, 16 November 2025 diff hist +29 Rust’s Firmware Revolution: How Memory Safety Stopped Our $2M Hardware Recall No edit summary current
  • 08:2008:20, 16 November 2025 diff hist +14,854 N 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:1908:19, 16 November 2025 diff hist +41 An idea for a GPU programming language feature: polysemous function type checking — Rust No edit summary current
  • 08:1608:16, 16 November 2025 diff hist +30,230 N 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:1308:13, 16 November 2025 diff hist +7,937 N 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 “..." current
  • 08:1208:12, 16 November 2025 diff hist +5,667 N 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..." current
  • 08:0908:09, 16 November 2025 diff hist +14,061 N 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..." current
  • 08:0708:07, 16 November 2025 diff hist +4,303 N 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...." current
  • 08:0508:05, 16 November 2025 diff hist +10,422 N 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..." current
  • 08:0308:03, 16 November 2025 diff hist +5,806 N 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..." current
  • 08:0108:01, 16 November 2025 diff hist +6,039 N 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)..." current
  • 07:5907:59, 16 November 2025 diff hist +7,551 N 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..." current
  • 07:5707:57, 16 November 2025 diff hist +17 Why Google, Microsoft, and the White House Chose Rust? No edit summary current
  • 07:5607:56, 16 November 2025 diff hist +7,416 N 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:5407:54, 16 November 2025 diff hist +12,936 N 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..." current
  • 07:5207:52, 16 November 2025 diff hist +16 Binary Diet: Shrinking Rust Releases Without Sorcery No edit summary current
  • 07:5207:52, 16 November 2025 diff hist +6,392 N 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:5007:50, 16 November 2025 diff hist +9,317 N 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..." current
  • 07:4907:49, 16 November 2025 diff hist −10 Profiling Rust Made Easy: cargo-flamegraph, perf & Instruments No edit summary current
  • 07:4807:48, 16 November 2025 diff hist +7,224 N 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:4607:46, 16 November 2025 diff hist +8,392 N 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..." current
  • 07:4407:44, 16 November 2025 diff hist +5,231 N 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 ..." current
  • 07:4207:42, 16 November 2025 diff hist +17,230 N 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..." current
  • 07:4107:41, 16 November 2025 diff hist +5,785 N 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..." current
  • 07:4007:40, 16 November 2025 diff hist +17,384 N 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..." current
  • 07:3507:35, 16 November 2025 diff hist +7,721 N 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..." current
  • 07:3307:33, 16 November 2025 diff hist +7,141 N 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..." current
  • 07:3107:31, 16 November 2025 diff hist +9,314 N 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..." current
  • 07:3007:30, 16 November 2025 diff hist +7,193 N 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..." current
(newest | oldest) View ( | ) (20 | 50 | 100 | 250 | 500)
Retrieved from "https://johnwick.cc/index.php?title=Special:Contributions/PC"