Rust recap for week 49/2023
From toNewsletter sent every monday with a recap of articles, projects and tutorials from previous week.
Articles #
-
How do I get better at Low level programming 282 comments in 18 discussions
-
Databases are the endgame for data-oriented design 255 comments in 4 discussions
-
On inheritance and why it's good Rust doesn't have it 207 comments in 2 discussions
-
Common Rust Lifetime Misconceptions (2020) 182 comments in 5 discussions
-
Loco: the one-person framework for Rust for side-projects and startups 128 comments in 3 discussions
-
Dump C++ and in Rust you can trust, Five Eyes agencies urge 60 comments in 1 discussion
-
Blog Post: Non-Send Futures When? 41 comments in 2 discussions
-
On the Dual Nature of Necessity in Use of Rust Unsafe Code 32 comments in 1 discussion
-
trippy: network diagnostic tool 32 comments in 1 discussion
-
Announcing Rust 1.74.1 | Rust Blog 30 comments in 1 discussion
-
A guide to getting started with Axum - 0.7 changes included 30 comments in 2 discussions
-
Highest Paying Rust Companies 29 comments in 1 discussion
-
What I learned with Rust during 1 year exactly 27 comments in 1 discussion
-
Blog: Operating Systems - Spinlocks 26 comments in 2 discussions
-
Behind the Scenes of Rust String Formatting: format_args!() 20 comments in 1 discussion
Releases #
-
faer 0.16 release, a general purpose (dense/sparse) linear algebra library 299 comments in 17 discussions
-
Skytable Octave released: BlueQL, injection protection, expressive querying, performance improvements and more 36 comments in 4 discussions
Projects #
-
The Rust compiler backend for .NET can now compile std with (numerous) errors, and supports allocation (Box, Vec, String, etc.) 193 comments in 6 discussions
-
Announcing iMessage Exporter 1.8.0: Velvet Ash 188 comments in 8 discussions
-
Youki: A container runtime written in Rust 71 comments in 5 discussions
-
[OC] A chess game in the terminal 🦀 61 comments in 3 discussions
-
Flowistry: an IDE plugin that analyzes the information flow of Rust programs, showing whether it's possible for one piece of code to affect another 50 comments in 3 discussions
-
Chess in the type-systems of Rust and TypeScript 26 comments in 2 discussions
-
Helm-like templating tool for docker-compose written in Rust 25 comments in 2 discussions
-
Polars: Dataframes powered by a multithreaded query engine, written in Rust 23 comments in 2 discussions
-
Modular audio synthesizer written in Rust 17 comments in 2 discussions
-
Loco: Rust framework for side projects and startups 12 comments in 2 discussions
Videos #
-
Linus on Rust in the Linux kernel (December 2023) 67 comments in 1 discussion
-
What's Zig got that C, Rust and Go don't have? [video] 65 comments in 3 discussions
-
HackeRPG - First Gameplay Trailer 16 comments in 1 discussion
-
Announcing mfio - Completion I/O for Everyone 12 comments in 1 discussion
-
Trace Me a River: Computing stuff on GPU using Rust; live coding, video | code::dive 2023 4 comments in 1 discussion
-
Optimizing Rust code with flamegraphs and benchmarks 2 comments in 1 discussion
This is an archived issue from the Rust newsletter.