I always like "by example"s for learning languages - here’s Rust’s.

I’d probably make a project with it. Maybe a CLI tool using clap_derive and some crate that does something neat that you want to do. Depends what you’re interested in I guess.

I wouldn’t recommend trying to do leetcode problems with Rust because they are obsessed with linked lists and linked lists are awkward in Rust.

Also I wouldn’t recommend making a game or GUI app with Rust yet since the ecosystems there are immature.

A microcontroller project using Embassy is probably a fun way to learn too but I haven’t actually tried it yet.

Yeah I feel like it was more than 3 years ago but I guess it’s been a long 3 years!

https://blog.rust-lang.org/2022/08/05/nll-by-default/

Yeah I think the reputation was probably deserved early in Rust’s life, but as time has gone on it has gotten a lot easier to write, especially with the non-lexical lifetimes update 3 years ago.

It’s better than nothing but it really only drags Bash from “your code is definitely horribly broken” to “your code is probably broken”. Nothing like Rust!

8 GB is a really small amount. Even phones have had that much RAM for several years. The average desktop I built in 2012 had 16 GB of RAM.

Plenty of modern computers only come with a small amount of RAM, because most people only need a small amount, but 8 GB is still a small amount.

He also thought that Rust integrates poorly into project with a deep C++ OOP hierarchy. That is probably still true as well.

Is there any language that can do that? As far as I know there isn’t. You can use SWIG or whatever but it’s just as awful as any Rust/C++ interop. There’s Carbon, but that’s a work in progress.

IMO if you need integration with a deep C++ OOP hierarchy your options are a) give up and just use C++, or b) pain, no matter what language you target.

Sounds like you know plenty to learn Rust.

I came for the trash Phoronix comments… But actually they were all very reasonable! What happened to the anti-Rust luddites?

Rust doesn’t have inheritance like in traditional OOP languages because it doesn’t have virtual methods. You have to manually implement methods to delegate to base classes.

Also what is this trash meme?

Ah that’s way more progress than I thought! Last I heard they were still in “you’re wrong for wanting this” territory.

How are those namespaces getting on?

Using a function is strictly worse than figuring out the formatting at compile time (something Zig also does).

The derives are just shortcuts. You can write everything out long-hand like you would in C++ or Python too if you really want.

Honestly both of these complaints are essentially “why does Rust use macros to make writing code better/easier?”.

code often contains backticks

I’ve never seen code contain three backticks though.

I guess your heading logic kind of makes sense but tbh I still hate it.

Very weird style. Inconsistent heading styles. Four tilde code blocks? That’s totally nonstandard. Why?

Yeah unfortunately these numbers don’t really allow any conclusions to be drawn at all.

Also they’re not really related to supply chain security which is more about deliberate subterfuge. I think the interesting stat there would be how many authors are being trusted typically for each crate.

It’s just not a very good name. Awkward even without the mpreg/preg thing. Steps on ffmpeg’s toes too much. Just pick something unique. Videoh. Muxy. Movrify. Flippityflop, whatever. I thought about those names for literally 10 seconds. You can definitely do better than ffmpreg if you think harder!

I mean, it would be great if this succeeded… ffmpeg is nice and all but its interface is clearly terrible and there’s absolutely no way it is remotely secure. Anyone that uses it on a server basically has to run it in its own VM, or a severely locked down sandbox.

But good luck supporting all the codecs people expect. I’m not even talking the obscure ones ffmpeg supports; just the ones “normal” people use will be a life’s work.

Also you have to change the name!

That is not actually a “data race”. It is a race condition for sure, but a data race is a very specific thing - where two threads access the same location at the same time and at least one is a write.

That could be unsafe in Rust because it might lead to reading “impossible values” like an enum that isn’t equal to any of its variants. Therefore safe Rust must prevent it or there’s a soundness hole.

Doesn’t say anything you didn’t already know. Probably written with AI.

Also the conclusion is wrong:

Neither approach is universally superior.

The Rust approach is obviously superior.

it has modules for everything

Not everything. PyYAML, Pydantic and Typer are things I commonly want in scripts that aren’t in the standard library.

Simply do pip install anything. But best practice is to use a python virtual environment and install packages into that one.

It’s more than “best practice”. It’s mandatory on many recent Linux distros. And yeah setting up a venv and installing dependencies is not something you want to have to do for each script you run.

Its one of the slowest to write code in.

It depends what your goal is. If you want robust code that works reliably then I would say Rust has the edge still. Yes it will take longer to write but you’ll spend way less time debugging it and writing tests.