New pages

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)...")
07:5907:59, 16 November 2025 If StackOverflow Had Feelings, It Would Be Written in Rust (hist | edit) [7,551 bytes] PC (talk | contribs) (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:5607:56, 16 November 2025 Why Google, Microsoft, and the White House Chose Rust? (hist | edit) [7,433 bytes] PC (talk | contribs) (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 Bridging Two Worlds: Integrating Rust with Go Using CGo (hist | edit) [12,936 bytes] PC (talk | contribs) (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:5207:52, 16 November 2025 Binary Diet: Shrinking Rust Releases Without Sorcery (hist | edit) [6,408 bytes] PC (talk | contribs) (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 I Built My Own AI Girlfriend in Rust — And She Actually Remembers Me (hist | edit) [9,317 bytes] PC (talk | contribs) (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:4807:48, 16 November 2025 Profiling Rust Made Easy: cargo-flamegraph, perf & Instruments (hist | edit) [7,214 bytes] PC (talk | contribs) (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 Rust — 7 Essential Crate That Will Instantly Elevate Your Project in Rust (hist | edit) [8,392 bytes] PC (talk | contribs) (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:4407:44, 16 November 2025 Meet Puhu: A Fast Python Image Library (with a Secret Rust Core) (hist | edit) [5,231 bytes] PC (talk | contribs) (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:4207:42, 16 November 2025 Rust in the Backend: When (and When Not) to Replace Your Node/Python Services (hist | edit) [17,230 bytes] PC (talk | contribs) (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:4107:41, 16 November 2025 Fixing Rust’s “linker cc not found” on Debian (WSL on Windows 10): A Clear, No-Nonsense Guide (hist | edit) [5,785 bytes] PC (talk | contribs) (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:4007:40, 16 November 2025 Rust Data Structures: Vec T, & T , Box T. Do You Really Understand Collection Containers? (hist | edit) [17,384 bytes] PC (talk | contribs) (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:3507:35, 16 November 2025 Finally Understanding Rust Ownership: A Visual Guide (hist | edit) [7,721 bytes] PC (talk | contribs) (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:3307:33, 16 November 2025 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 (hist | edit) [7,141 bytes] PC (talk | contribs) (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:3107:31, 16 November 2025 7 Hard Security Wins Rust Guarantees — And 9 Traps It Won’t Save You From (hist | edit) [9,314 bytes] PC (talk | contribs) (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:3007:30, 16 November 2025 Is it possible to cause a memory leak in Rust? (hist | edit) [7,193 bytes] PC (talk | contribs) (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:2807:28, 16 November 2025 Inside the Borrow Checker: How Rust Validates Lifetimes in MIR (hist | edit) [11,386 bytes] PC (talk | contribs) (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:2707:27, 16 November 2025 How to Get a Slice as an Array in Rust (Without Losing Your Mind) (hist | edit) [6,941 bytes] PC (talk | contribs) (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:2507:25, 16 November 2025 How Miri Simulates Rust’s Memory Model for Undefined Behavior Detection (hist | edit) [8,144 bytes] PC (talk | contribs) (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:2407:24, 16 November 2025 What If Rust Ran in the Browser Natively — Without WebAssembly? (hist | edit) [7,904 bytes] PC (talk | contribs) (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:0201:02, 16 November 2025 What Is the Equivalent of the join Operator Over a Vec String in Rust? (hist | edit) [7,464 bytes] PC (talk | contribs) (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:0101:01, 16 November 2025 Futures and Wakers Explained — The Real Async Engine Inside Rust (hist | edit) [10,560 bytes] PC (talk | contribs) (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:5900:59, 16 November 2025 Google Launches Magika 1.0: Rust-Powered AI Engine Doubles File Type Detection Capabilities (hist | edit) [5,175 bytes] PC (talk | contribs) (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:5800:58, 16 November 2025 Rust-cargo-docs-rag-mcp (hist | edit) [662 bytes] PC (talk | contribs) (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:5700:57, 16 November 2025 What Learning Rust Taught Me About My Java Code (hist | edit) [8,557 bytes] PC (talk | contribs) (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:5600:56, 16 November 2025 7 Boring Rust Sidecar Wins — Cut Memory 40% Without Rewrites (hist | edit) [8,474 bytes] PC (talk | contribs) (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:5300:53, 16 November 2025 Rust is King, But Java’s Project Loom Just Changed the Game (hist | edit) [15,101 bytes] PC (talk | contribs) (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:5200:52, 16 November 2025 Rust, ORT, ONNX: Real-Time YOLO on a Live Webcam- Part 3 (hist | edit) [16,674 bytes] PC (talk | contribs) (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:5100:51, 16 November 2025 Learning Rust Part 2 — Data Layout and Enums in Practice (hist | edit) [25,451 bytes] PC (talk | contribs) (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:4900:49, 16 November 2025 Building a High-Performance Orderbook Aggregator in Rust (hist | edit) [6,808 bytes] PC (talk | contribs) (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:4800:48, 16 November 2025 The Pin API Explained: Why Rust’s Async Needs This Complexity (hist | edit) [6,652 bytes] PC (talk | contribs) (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:4500:45, 16 November 2025 The White-Collar Rust Belt (hist | edit) [7,753 bytes] PC (talk | contribs) (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...")
00:4400:44, 16 November 2025 Initialize a large, fixed-size array with non-Copy types in RUST (hist | edit) [6,605 bytes] PC (talk | contribs) (Created page with "Summary Need [Option<Box<T>>; N] without Copy or Clone? * Rust ≥ 1.79: let a: [Option<Box<T>>; N] = [const { None }; N]; * Rust ≥ 1.63: let a = std::array::from_fn(|_| None); (works with any initializer logic!) * Rust ≥ 1.38: const INIT: Option<Box<T>> = None; let a = [INIT; N]; (initializer must be a const-eval value) If you’ve ever tried to initialize a fixed-size array of a nullable, non-copyable type in Rust — say, Option<Box<Thing>>...")
00:4200:42, 16 November 2025 From JavaScript to Rust: A Web Developer’s Journey Into Systems Programming (hist | edit) [10,209 bytes] PC (talk | contribs) (Created page with "The browser console blinks at you. undefined is not a function. You fix it in thirty seconds, refresh the page, move on. That's the rhythm of JavaScript—quick feedback, instant gratification, problems that resolve with a page reload. Then you open a Rust file for the first time and everything slows down. Like, dramatically slows down. You’re not alone in feeling that whiplash. A 2024 Stack Overflow survey found that 68% of web developers who tried systems programmi...")
00:4100:41, 16 November 2025 Are Globals in Rust a Bad Idea… or a Necessary Evil? (With SQLite Examples) (hist | edit) [8,568 bytes] PC (talk | contribs) (Created page with "If you’re coming to Rust from C/C++ or scripting languages, “just make it global” can feel like the easiest way to share state — like a database handle — across a bunch of functions. Rust pushes back hard on that instinct, and for good reasons (safety, testability, concurrency). But sometimes a single, shared “thing” really is central to your program. So: Can you use globals in Rust? Yes. Should you? Usually no — but sometimes yes, if you do it the...")
00:4000:40, 16 November 2025 My Rust Server Handles 100k Concurrent Users (And Here’s the Proof): Part 2 (hist | edit) [6,807 bytes] PC (talk | contribs) (Created page with "In the previous tutorial, “Blazingly Fast Rust Server from scratch– 100k connections like it’s nothing (Part 1)”, I claimed that my Rust server can handle 100k connections, yet I provided no proof! In this article, I will discuss the tests I performed to corroborate the outrageous claim. The setup is rather empirical because, along the way of stress testing our server, we learned a lot. However, after some trial and error, we got the proof we needed — we can h...")
00:3700:37, 16 November 2025 Rust vs OCaml in 2025 — Benchmarks, Binary Sizes, and a 10-Minute Decision Tree (hist | edit) [9,730 bytes] PC (talk | contribs) (Created page with "You are choosing a language for real work. You care about speed, but you also care about sleep. You want control without turning your day into a wrestling match. This is a straight walk through Rust and OCaml in 2025 with one goal: help you ship and feel proud of the choice. No drama. No noise. Just what matters for performance, footprint, and day-to-day flow. What You’ll Walk Away With * A decision path you can follow right now * Two allocation-aware code...")
00:3500:35, 16 November 2025 Rust’s Two Kinds of mut: Binding vs. Borrow (and how to pick the right one) (hist | edit) [6,177 bytes] PC (talk | contribs) (Created page with "Rust has two places where you’ll see mut, and they mean different things: * Before a variable name (mut foo): makes the binding mutable — you can reassign it, and you can borrow it mutably. * Inside the type (&mut T): makes the reference mutable — you’re allowed to mutate the thing it points to. If you keep just that sentence in your head, 90% of the confusion goes away. Let’s unpack it with the exact signatures you saw, why the mut moves aroun...")
00:3300:33, 16 November 2025 Fine Tuning Models in PyTorch & Using ONNX for Inference in Python & Rust (hist | edit) [29,391 bytes] PC (talk | contribs) (Created page with "[1] Overview I want to mostly focus on the Inference side of things and how ONNX can be leveraged, but to get there I want to cover fine tuning a model to serve as a starting point and as a working example. Then I will dive into the specifics of how to use ONNX for inference in both rust and python, also covering how some of the pre-processing transforms can be replicated without having to rely on the transforms used in PyTorch. Here is why ONNX can be advantageous — w...")
00:3100:31, 16 November 2025 The M:N Scheduler Problem: How Rust Futures and Go Goroutines Handle Thread-Bound I/O (hist | edit) [5,684 bytes] PC (talk | contribs) (Created page with "Your p95 dies when one syscall grabs the only thread — here is how to fence it in. I watch a clean async service stall after a single DNS call blocks the wrong thread and drags p95 up by 37 percent. Futures look busy. Goroutines look plenty. The reactor has work. The scheduler does not. I need to separate real nonblocking work from code that clings to an OS thread. The fix is not magic. It is placement. When thread-bound I/O stalls everything A neat M:N runtime colla...")
00:3000:30, 16 November 2025 Best Blockchain Dev Pathway for 2026: EVM, Rust, or TON? (hist | edit) [6,070 bytes] PC (talk | contribs) (Created page with "As we move toward 2026, the blockchain development landscape is evolving rapidly. Protocols are pushing for higher throughput, richer smart-contract capabilities, deeper cross-chain integration, and tighter ties between Web3 and traditional stacks. Meanwhile, the dev tooling in 2025 has matured — offering frameworks, SDKs, infrastructure, and patterns that set the stage. For teams planning new dApps, protocols, or infrastructure through 2026, understanding where the ec...")

16 November 2025