A Rick-roll in the source code

Rust is the best language so far to replace today's most used crypto libraries: OpenSSL, BoringSSL and libsodium.

C libraries often contain a lof of assembly code making them really fast, but potentially unsafe.
pure-Rust libraries benefit from Rust strong typing and generally offer a better API, compile for all platforms including WebAssembly.

It's important to note that pure-Rust libraries might be slightly slower than C and assembly wrappers, but still fast enough for most use cases.

• aws-lc-rs is a cryptograhy create
• libcrux is a Rust wrapper for formally verified C, Assembly and Rust code.
• ring is focused on the implementation, testing, and optimization of a core set of cryptographic operations exposed via an easy-to-use (and hard-to-misuse)
• boring is a safe wrapper around google's boringssl
• dalek-cryptography is a Github organization about pure-Rust elliptic curve cryptography, used by Signal and Diem
• graviola is promising because it's faster than other projects, but not mature enough yet.

There is also blake3

In short, RustCrypto to get pure-Rust implenentations, or aws-lc-rs for linux-servers and best perforamances with FIPS certification.

RustPython is a Python interpreter written in Rust. RustPython can be embedded into Rust programs to use Python as a scripting language for your application, or it can be compiled to WebAssembly in order to run Python in the browser. RustPython is free and open-source under the MIT license.

It would be to go to to use Python in the browser because RustPython can compile in WebAssembly.

The playground: https://rustpython.github.io/demo/

I’m currently building an app that pulls a ton of data from an external API. If you use Rust, you know the drill: you get a UserDTO from the API, but you want a User in your domain. This usually leads to writing the same From trait implementation over and over again.

What’s in the sandbox so far? I built a macro called FromDTO. Instead of manually mapping dozens of fields, I can just do this:

Note the serde create do that for JSON and other formats

Rust devs who want async.
Rust devs who understand Rust's type system.
People who like BSDM.

13 references one pointing to another. It's the maximum Rust ensure to support.

So why 14?
Seems like because Rust thinks that 13 references ought to be enough for anybody.

More about https://www.computerworld.com/article/1563853/the-640k-quote-won-t-go-away-but-did-gates-really-say-it.html

The semantic of Rust make it good to be produced by AI.

concurrency with Semaphore, async and Arc data structures to retrieve as fast as possible files stored on S3

Readur is a powerful and modern document management system designed to help individuals and teams efficiently organize, process, and access their digital documents. It combines a high-performance backend with a sleek and intuitive web interface to deliver a smooth and reliable user experience.

Les ressources nécéssaires sont cependant insuffisante pour un Raspberry Pi. D'autres alternatives existent comme PaperMerge ou bien Paperless ngx

(via https://korben.info/readur-gestion-documentaire-ocr-rust-autoheberge.html)

The first game written and played entirely in Rust's type system. Not just do you play by writing Rust code, the rules of the game are enforced by the Rust compiler! If you can write the program so it compiles and doesn't panic, you win!

A cross platform UI library to build to apple, android, web.

The project is available under https://github.com/water-rs/waterui

1. They split the code into crates that are independent of the rust of the system.
2. Start with src/main.rs or src/lib.rs to get a high level overview then go down into the things you need to understand in more detail.
3. The trick to be productive in a large codebase is thus simple: focus, one step at a time.

Tips for the documentation:

Here's advice I figured out a while ago: if you'd doing something user-facing, write the documentation. When someone asks a question, point to the place in the documentation that answers it and ask if that clarifies. If they are still confused, instead of answering them, improve the documentation, and ask them if that helped. Very quickly you get to the point where the documentation is accurate even for people who don't know the answers already.

Fast, flexible mock API server powered by JSON configuration and a lightweight scripting language (rjscript).

New generation of tools:

• Speedy Web Compiler
• ESBuild
• BiomeJS t combines code formatting and linting into a single high-performance JavaScript toolchain.
• Oxc is a collection of Rust-based Javascript tools focusing on linting, formatting and transforming Javascript and typescript tools.
• Fast Node Manager / Mise
• Typescript in Go

Another notable efforts are Turbopack and Turborepo, Bun and Deno.

Contributing becomes less accessible to the majority of JavaScript developers of course. The shift demonstrates other skills in system programming that will drive even more innovative tooling in the coming years

A few percents in wall-time improvments this year