fz 2.0.0 NEXUS — package manager, BLAKE3 cache, and cross-compilation for C/ASM
Yesterday I shipped 1.9.0. Got a solid mix of hate and genuinely useful feedback. Didn't sleep. Took all of it personally. Built 2.0.0 instead.
No point dragging it out — here's everything I promised, shipped right now.
What's new
⚡ BLAKE3 file hashing — 7x faster cache
Dropped SHA256. Switched to BLAKE3 across the board.
Package verification from the catalog uses BLAKE3 too.
📦 Package manager — fz pm
The big one. Dependency management for C/ASM projects that doesn't make you want to quit programming.
Dependencies live in
🔌 Shared library support
New flags:
🎯 Cross-compilation
ARM, RISC-V, x86_64, i386. Compiler, assembler, and linker are selected automatically for the target triple.
🗂 Static libraries
Builds
🧠 LSP support
Generates
Improvements & fixes
● Parallel builds with
● Linker scripts and text section address:
● Fixed object file name collisions (
● All
● Context and timeouts for all network and git operations
● Test coverage: utils 84%, linker 60%, assembler 60%, builder 56%
Install
Links
● Repository: https://github.com/forgezero-cli/ForgeZero
● Package catalog: https://github.com/forgezero-cli/catalog
● Docs: https://github.com/forgezero-cli/ForgeZero#readme
Solo project. All issues and PRs read personally. If something's broken or missing — tell me, I'll probably fix it overnight.
via DEV Community: rust (author: Alex Voste)
Yesterday I shipped 1.9.0. Got a solid mix of hate and genuinely useful feedback. Didn't sleep. Took all of it personally. Built 2.0.0 instead.
No point dragging it out — here's everything I promised, shipped right now.
What's new
⚡ BLAKE3 file hashing — 7x faster cache
Dropped SHA256. Switched to BLAKE3 across the board.
Package verification from the catalog uses BLAKE3 too.
📦 Package manager — fz pm
The big one. Dependency management for C/ASM projects that doesn't make you want to quit programming.
fz pm add <repository>
fz pm remove <package>
fz pm update
fz pm list
fz pm search <query>
fz pm install
fz pm catalog
Dependencies live in
.fz.yaml. Removal cleans up empty parent directories automatically. Backed by a community-driven JSON package catalog.🔌 Shared library support
New flags:
-shared, -cc-flag, -ld-flag. Build .so and .dylib targets without wiring things up by hand.🎯 Cross-compilation
fz -target arm-linux-gnueabihf
fz -target riscv64-linux-gnu
fz -target x86_64-w64-mingw32
ARM, RISC-V, x86_64, i386. Compiler, assembler, and linker are selected automatically for the target triple.
🗂 Static libraries
fz -type static -lib mylib
Builds
.a archives from object files via ar.🧠 LSP support
fz -compile-commands
Generates
compile_commands.json for clangd and any compatible LSP client. Autocomplete and go-to-definition, no manual config.Improvements & fixes
● Parallel builds with
-j N● Linker scripts and text section address:
-T, -Ttext● Fixed object file name collisions (
hello.asm vs hello.s)● All
golangci-lint warnings resolved: errcheck, govet, ineffassign● Context and timeouts for all network and git operations
● Test coverage: utils 84%, linker 60%, assembler 60%, builder 56%
Install
go install github.com/forgezero-cli/ForgeZero/cmd/fz@latest
Links
● Repository: https://github.com/forgezero-cli/ForgeZero
● Package catalog: https://github.com/forgezero-cli/catalog
● Docs: https://github.com/forgezero-cli/ForgeZero#readme
Solo project. All issues and PRs read personally. If something's broken or missing — tell me, I'll probably fix it overnight.
via DEV Community: rust (author: Alex Voste)
Is Gemini 3.5 Flash Actually Better at Coding Than 3.1 Pro? I Tested It with Real Rust Code
via DEV Community: rust (author: hiyoyo)
via DEV Community: rust (author: hiyoyo)
Telegraph
Is Gemini 3.5 Flash Actually Better at Coding Than 3.1 Pro? …
Background Gemini 3.5 Flash launched at Google I/O 2026 with a bold claim: it beats Gemini 3.1 Pro on coding and agentic benchmarks — while running 4x faster. At the same time, X (formerly Twitter) is full of posts saying it hallucinates constantly and doesn't…
Rust Concepts: Macros, Modules, Testing & Unsafe Rust (Part 3)
via DEV Community: rust (author: mihir mohapatra)
via DEV Community: rust (author: mihir mohapatra)
Telegraph
Rust Concepts: Macros, Modules, Testing & Unsafe Rust (Part …
This is Part 3 of the Core Rust Concepts series. Part 1 — Ownership, Borrowing, Lifetimes, Traits, Result/Option, Pattern Matching Part 2 — Closures, Iterators, Generics, Enums, Smart Pointers, Async/Await Table of Contents Macros Modules & the Cargo Ecosystem…
I Built a Next-Gen DNS Diagnostic CLI in Rust That Visualizes DNSSEC Trust Chains
via DEV Community: rust (author: kent-tokyo)
via DEV Community: rust (author: kent-tokyo)
Telegraph
I Built a Next-Gen DNS Diagnostic CLI in Rust That Visualize…
If you've ever tried to debug a DNSSEC misconfiguration using dig, you know the pain. You're staring at a wall of raw text, manually cross-referencing DS records against DNSKEY records, tracing through TLD delegations one query at a time. It works — but it's…
Rust Concepts: Macros, Modules, Testing & Unsafe Rust (Part 3)
via DEV Community: rust (author: mihir mohapatra)
via DEV Community: rust (author: mihir mohapatra)
Telegraph
Rust Concepts: Macros, Modules, Testing & Unsafe Rust (Part …
This is Part 3 of the Core Rust Concepts series. Part 1 — Ownership, Borrowing, Lifetimes, Traits, Result/Option, Pattern Matching Part 2 — Closures, Iterators, Generics, Enums, Smart Pointers, Async/Await Table of Contents Macros Modules & the Cargo Ecosystem…
I Just Wanted to Reuse Async Functions in Rust. I Ended Up Building a Tiny Task Manager
via DEV Community: rust (author: icsboyx)
via DEV Community: rust (author: icsboyx)
Telegraph
I Just Wanted to Reuse Async Functions in Rust. I Ended Up B…
I Just Wanted to Reuse Async Functions in Rust. I Ended Up Building a Tiny Task Manager I am currently studying Rust, and one of the things that kept bothering me was surprisingly simple: How do I reuse an async function more than once in a clean way? At…
Web Developer Travis McCracken on Rate Limiting at the Edge: A Backend Strategy
via DEV Community: rust (author: Travis McCracken Web Developer)
via DEV Community: rust (author: Travis McCracken Web Developer)
Telegraph
Web Developer Travis McCracken on Rate Limiting at the Edge:…
Harnessing Power with Rust and Go: A backend developer's journey Hello, fellow developers! I’m Web Developer Travis McCracken, and today I want to share some insights into my work with backend development, especially with two of the most exciting programming…
Ditching Geo-Restrictions in Crypto Stores is Harder Than It Looks
via DEV Community: rust (author: pretty ncube)
via DEV Community: rust (author: pretty ncube)
Telegraph
Ditching Geo-Restrictions in Crypto Stores is Harder Than It…
The Problem We Were Actually Solving I still remember the day I was tasked with setting up an admin dashboard for our crypto digital store. The catch - we were operating in a country with strict financial regulations, which made it impossible to use conventional…
Building a native terminal for AI coding agents in Rust + GPUI
via DEV Community: rust (author: Arthur Jean)
via DEV Community: rust (author: Arthur Jean)
Telegraph
Building a native terminal for AI coding agents in Rust + GP…
Author: Arthur Jean, solo indie maker. More on paneflow.dev and arthurjean.com.Repo: github.com/ArthurDEV44/paneflow. MIT licensed. I spend my days running Claude Code, Codex, and OpenCode in parallel panes. Different agents on different branches, each with…
The Day Our Payment System Died at 3 AM From a False Positive in a Blacklist
via DEV Community: rust (author: pretty ncube)
via DEV Community: rust (author: pretty ncube)
Telegraph
The Day Our Payment System Died at 3 AM From a False Positiv…
The Problem We Were Actually Solving In 2023 we launched a SaaS tool for performance engineers. Nothing fancy—just a low-latency endpoint profiler that ingests traces and returns flamegraphs with flamegraph.js. We didnt need Stripes UI. We needed a way to…
Claude returned ```json blocks 14% of the time. Here is the Rust crate I wish I had earlier.
via DEV Community: rust (author: Mukunda Rao Katta)
via DEV Community: rust (author: Mukunda Rao Katta)
Telegraph
Claude returned ```json blocks 14% of the time. Here is the …
I had a system prompt that ended with: Reply with only a JSON object. Do not include code fences. Do not include explanation. That should be enough. It is not. Over a week of structured-output calls (12,400 of them, mostly Claude Sonnet 4.5 and 4.7), I logged…
Our retry loop made an outage worse. The circuit breaker stopped the cascade.
via DEV Community: rust (author: Mukunda Rao Katta)
via DEV Community: rust (author: Mukunda Rao Katta)
Telegraph
Our retry loop made an outage worse. The circuit breaker sto…
A few weeks back there was a 22-minute window where Anthropic returned a high rate of 5xx responses. Not a full outage. Degraded. Our agent service had a retry policy that backed off and tried again on 5xx. With six workers and a shared retry budget that…
The Day Our Latency Shot Up When the Runtime Decided to GC
via DEV Community: rust (author: pretty ncube)
via DEV Community: rust (author: pretty ncube)
Telegraph
The Day Our Latency Shot Up When the Runtime Decided to GC
The Problem We Were Actually Solving We needed a way to move money out of countries where PayPal, Stripe, and Gumroad had no footprint. Our micro-payment layer already integrated with local aggregators—EasyPaisa in Pakistan, bKash in Bangladesh, Flutterwave…
Chat With Your Documents Using Garudust Agent — No Vector Database Required
via DEV Community: rust (author: Garudust)
via DEV Community: rust (author: Garudust)
Telegraph
Chat With Your Documents Using Garudust Agent — No Vector Da…
Most RAG tutorials start the same way: "First, install a vector database…" Then come the embedding models, the chunking strategies, the similarity thresholds. By the time you can ask a question about a PDF, you've deployed three services and written 200 lines…
React 19 Hydration Errors & Rust Async Traits: Two Deep Dives
via DEV Community: rust (author: gunturss24)
via DEV Community: rust (author: gunturss24)
Telegraph
React 19 Hydration Errors & Rust Async Traits: Two Deep Dives
React 19 Hydration Mismatch — Root Cause & Fix If you've upgraded to React 19 and started seeing hydration errors like: Error: Hydration failed because the initial UI does not match what was rendered on the server. Here's the actual root cause and how to…
Cron & Scheduled Tasks in Garudust Agent — Autonomous Agents That Run Without You
via DEV Community: rust (author: Garudust)
via DEV Community: rust (author: Garudust)
Telegraph
Cron & Scheduled Tasks in Garudust Agent — Autonomous Agents…
Most AI agents wait. They sit idle until a human types something, respond, then go back to waiting. Garudust Agent can be different. With garudust-cron, you schedule tasks using standard cron syntax — the agent wakes up, runs a full LLM loop with all its…
Solving Global Ecommerce with Crypto — Why I Ditched Traditional Payment Processors
The Problem We Were Actually Solving
The real problem wasn't the users themselves, but the fact that these platforms had significant restrictions on where they operated. Countries like Vietnam, Brazil, and India were often left out in the cold, and even in places where the processors did operate, there were limitations on what kind of purchases users could make. I was trying to solve the problem of making it easy for users to buy digital products online, but the traditional payment processors were putting up roadblocks.
What We Tried First (And Why It Failed)
My initial solution was to just use the existing payment processors and hope for the best. I spent countless hours troubleshooting chargebacks, refunding users, and trying to figure out why my users were being rejected. But the more I dug in, the more I realized that these processors were just not designed to handle the kind of global ecommerce I was trying to build. They were rigid, inflexible, and ultimately, not worth the headaches.
The Architecture Decision
It was then that I turned to cryptocurrency. Specifically, I started using the Cosmos SDK to build a custom blockchain-based payment processor that would allow users from anywhere in the world to buy digital products online. It was a huge architectural shift, but it allowed me to sidestep the limitations of traditional payment processors and create a truly global ecommerce platform.
What The Numbers Said After
The numbers were staggering. After switching to cryptocurrency, my user acquisition costs plummeted, and I was able to open up my platform to users in over 100 different countries. Chargebacks went from a whopping 20% of all transactions to nearly 0%. And the most surprising statistic? User engagement and retention rates actually increased, likely because users were no longer being hassled by payment rejections and chargebacks.
What I Would Do Differently
Looking back, I wish I had explored cryptocurrency sooner. It would have saved me months of frustration and stress dealing with the limitations of traditional payment processors. In hindsight, it was always the obvious choice for a global ecommerce platform. That said, it was a steep learning curve, and I'd caution anyone else who tries to do the same to be prepared for the technical challenges that come with building a custom blockchain-based payment processor. But the results are well worth it.
via DEV Community: rust (author: pretty ncube)
The Problem We Were Actually Solving
The real problem wasn't the users themselves, but the fact that these platforms had significant restrictions on where they operated. Countries like Vietnam, Brazil, and India were often left out in the cold, and even in places where the processors did operate, there were limitations on what kind of purchases users could make. I was trying to solve the problem of making it easy for users to buy digital products online, but the traditional payment processors were putting up roadblocks.
What We Tried First (And Why It Failed)
My initial solution was to just use the existing payment processors and hope for the best. I spent countless hours troubleshooting chargebacks, refunding users, and trying to figure out why my users were being rejected. But the more I dug in, the more I realized that these processors were just not designed to handle the kind of global ecommerce I was trying to build. They were rigid, inflexible, and ultimately, not worth the headaches.
The Architecture Decision
It was then that I turned to cryptocurrency. Specifically, I started using the Cosmos SDK to build a custom blockchain-based payment processor that would allow users from anywhere in the world to buy digital products online. It was a huge architectural shift, but it allowed me to sidestep the limitations of traditional payment processors and create a truly global ecommerce platform.
What The Numbers Said After
The numbers were staggering. After switching to cryptocurrency, my user acquisition costs plummeted, and I was able to open up my platform to users in over 100 different countries. Chargebacks went from a whopping 20% of all transactions to nearly 0%. And the most surprising statistic? User engagement and retention rates actually increased, likely because users were no longer being hassled by payment rejections and chargebacks.
What I Would Do Differently
Looking back, I wish I had explored cryptocurrency sooner. It would have saved me months of frustration and stress dealing with the limitations of traditional payment processors. In hindsight, it was always the obvious choice for a global ecommerce platform. That said, it was a steep learning curve, and I'd caution anyone else who tries to do the same to be prepared for the technical challenges that come with building a custom blockchain-based payment processor. But the results are well worth it.
via DEV Community: rust (author: pretty ncube)