Developer Builds Exoroute, a Rust-Based AI Router Using Just 80 MB RAM

·11 views

A developer created Exoroute, a lightweight AI router built with Rust, after finding that its predecessor Omniroute consumed over 2.8 GB of RAM for just 11 connections. Exoroute addresses these resource efficiency concerns by running 14 concurrent users at roughly 1.3% CPU and 80 MB of RAM. The developer notes these benchmarks were recorded on a personal Linux device and may vary across different systems. Released as version 0.1.0, Exoroute is available for installation via npm and can be explored at exoroute.dev. The developer is actively seeking community feedback on this initial release.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Backpack Wallet Review: A Multi-Chain Crypto Wallet Built for DeFi and Beyond

Backpack is a self-custodial, cross-chain cryptocurrency wallet developed by CoralXYZ and founded by Solana developer Armani Ferrante in 2022. Originally associated with the Mad Lads NFT collection on Solana, the platform has since expanded into a full-featured ecosystem that includes a crypto exchange, margin and futures trading, lending services, and a regulated securities brokerage operating in over 150 countries. The wallet supports more than 15 blockchain networks — including Ethereum, Solana, Bitcoin, and several non-EVM chains — accessible through a single seed phrase across Android, iOS, and browser extension. As a non-custodial wallet, private keys and recovery phrases are generated and encrypted locally on the user's device, giving users full ownership of their assets. The broader Backpack ecosystem now comprises four core products: the Backpack Wallet, Backpack Exchange, Backpack Securities, and the Mad Lads NFT collection.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Fukurama.com Offers Branching AI Chat Workflow for Frontend Development

A developer has launched Fukurama.com, an AI-powered frontend tool designed to address the limitations of traditional linear AI chat interfaces. The platform allows users to branch off conversations, work through problems in isolation, and reintegrate results into the main workflow. This approach aims to keep complex, iterative development sessions more organized and manageable. The tool supports multiple AI providers, including OpenAI, Anthropic, Gemini, Deepseek, Openrouter, Qwen, and Kimi, and requires users to supply their own API key.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Thin AI Wrapper Cuts Confident Fabrication from 25.8% to 7.4%, but Accuracy Also Drops

Researchers at ShortSingh-covered platform tested five leading AI models on a corpus of documented-failure questions, running each model both bare and wrapped in a lightweight layer combining retrieved evidence with an abstention rule. Across the four models that accepted the treatment, confident wrong answers fell sharply from 25.8% to 7.4%, but overall correctness also declined from 43.9% to 21.3% as the wrapper pushed models to abstain rather than guess. DeepSeek v4 proved an outlier, continuing to affirm fabricated legal cases even when evidence was placed directly in front of it, confirming 12 of 15 non-existent cases as real. Claude Fable 5 refused the honesty wrapper entirely across all 295 test prompts, yet accepted identical instructions when reframed as an agent task with search tools, completing 620 of 620 calls without issue. The team emphasises that the results reflect a specific corpus of known failures under a single-draw setup and are not comparable to official benchmark scores or general model performance.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Freelancer's Scope Creep Lesson: Why Discounts Without Boundaries Cost More

A software developer recounts how a Canadian client negotiated a reduced rate for minor WordPress updates, which gradually expanded into a full site rebuild at the original discounted price. The developer completed the work but ended up losing both time and money due to unchecked scope creep. The core mistake, he explains, was not re-scoping the project each time the client added new requests beyond the original agreement. He now sets written scopes upfront, ties any discount explicitly to a reduced scope, and treats every out-of-scope request as a separate billable item. The experience led him to adopt a firm policy: if a revised price does not work for the client, he walks away rather than accept terms that guarantee an unprofitable engagement.

0 comments Read more at DEV Community