there is one place that gets less attention and yet has a colossal impact: building libraries for cross-platform applications.

Why would anybody want to go the "hard way" compiling Rust for multiple platforms?

1. Write once, run everywhere
2. Correctness
3. Security provided by Rust itself

The projects use two architecture:

• Either a cross-platform rust core with platform specific UI, state management and other dependencies
• Or platform specific user interface, state management and business logic that are bound together by many rust libraries

One thing is it seems easier than tmux to use

Examples to leverage rust designs to write better code

The benchmarks are lies.

Using a custom allocator such as jemalloc is recommended for all production Rust servers because the default libc allocator leads to too much memory fragmentation when pushed to its limits.

A tool-suit similar to Adobe, but open source and written in Rust.

Golem.de shared the news too: https://shaarli.lyokolux.space/shaare/E6txrA

RigSpark scores your hardware and gives every model a yes, slow or no verdict with estimated tok/s before you download. Then it verifies, serves and chats with your pick.

With Embassy it's seems reasonable to build without an OS. The first thing to try is esp32c6 (a dual-core RISC-V CPU running at 320MHz with Bluetooth, WiFi, USB and support for up to 32 MB of RAM).

Interesting point: it's currently something Rust can improve on.

It seems Rust is built for Parse, don't validate. The invariants are encoded in the type system.

• https://docs.rs/nonempty/latest/nonempty/ crates ensure .first() always return
• AbsPathBug is useful because Subsequent code doesn't have to validate the the path is absolute. The type enforces it.
• NonZero ensure the 0 value doesn't exist on the number type. Rust cam also optimize the memory used for Option<NonZero> by using the zero value as None.

The rewrite use FFI instead of a NodeJS subprocess. The rewrite occured component by component compared to Bun.

The agents used most of their time for reading and searching. It costs 120 000$ in tokens.

The rust version takes 55.3ms to create run on turn and dispose a client session; memory peak usage went from 1 383MB to 126 MB.

(from Let's get Rusty - AI loves rewriting codebases to Rust

Usually Rust framework compiles down to WASM.
Topcoat compiles to JS and use #[shard] to render UI if any of the function parameters changes, then it is rendered again on the server.

Topcoat is a modular, batteries-included Rust framework for building full-stack apps. It prioritizes simplicity and productivity.

Go is simpler but has a light overhead (2KiB per goroutine and 30 to 75 nanoseconds to spawn one), but Rust has a fragmented ecosystem where async is dependent of the runtime and the related functions comletely differ from the synchronous ones.

It shows how using RAM efficiently can increase performance.