It is interesting to note optimizations and arguments in favor of Rust

It seems to be a lighweight project. It's perfect for small projects!

There are now a whole new class of potential issues, design considerations, and challenges that Rust introduces to web developers which I think is often under-estimated.

Fixing one ownership issue often just shifts the problem to another place, and without a strong understanding of this mental model, it can be very difficult to identify which path from any given node is actually the "right" one, which gets closer to the real solution.

The documentation is awesome, but some crates are under-documented.

Editing Rust is not so much supported in VSCode than Typescript.

The feedback comes from a typescript developer.

Wikifunctions will use wasm and rust

Improve it to be project based:

• Evolution of the lines of code over time
• how much of language parts in the code base over time

...

A response in four steps to get started.

Display train/bus stops on a Kindle 😄

The author goes really in-depth 👍

All the most-impactful projects in the data engineering world are now written in Rust. More than the classics fast, safe and high-level language and C interop. The author provides highlight on:

The TL;DR is that most organizations don't even have that much [big] data, a few hundreds GB to single-digit TB for the 98%

One server is enough. [The industry] is instead focusing on simpler solutions.

Rust provides reusability! "For example, Arroyo, Ballista, delta-rs, InfluxDB and many more all use the Apache DataFusion query engine."

This is a massive piece of engineering that they don't have to re-invent themselves and can instead benefit from a software package built and continuously improved by many organizations that have a vested and shared interest in making it great.

• a new cargo info subcommand
• macOS on 64-bit ARM is now Tier 1
• mac Catalyst targets are now Tier 2
• precise capturing use<..> syntax
• native syntax for creating a raw pointer
• Safe items with unsafe extern: make code safe inside unsafe

and more low-level stuffs

An experiment to replace Nginx with Axum.

How to map integer types to rust integer types and more.

How to tackle C macros and inline functions in Rust?

Guo put together a ""hack"". His idea was to use Clang to compile helpers.c into LLVM bytecode. Then, for each Rust crate, ask the compiler to emit bytecode as well. Once everything is in the form of LLVM bytecode, it can be fed back into Clang with LTO turned on to produce a combined object file with the helpers inlined.

and more challenging topics.