> What are the chances of that, though?

The whole premise of the article is that they’re substantially lower, because some time for the ecosystem of dependency scanners and users to detect and report is better than none.

The check frequency isn't the problem, it's the latency between release and update. If a package was released 5 minutes before dependabot runs and you still update to it, your lower frequency hasn't really done anything.

https://www.igalia.com/2025/11/helpingvalve.html

It feels like perhaps you’ve conflated the issue in this thread, which is about using Rust in apt, which is much, much later in the distribution bringup than this bootstrapping, and using Rust in something like the Linux kernel, which is more relevant to those types of bootstrapping discussions you posted.

apt is so late in the process that these bootstrapping discussions aren’t quite so relevant. My point was that at the same layer of the OS, there are many, many components that don't meet the same criteria posted, including perl.

> I think this is the wrong way to promote rust

This is entirely the wrong lens. This is someone who wants to use Rust for a particular purpose, not some sort of publicity stunt.

> I know nobody that programms or even thinks about rust. I’m from the embedded world a there c is still king.

Now’s a good time to look outside of your bubble instead of pretending that your bubble is the world.

> as long as the real money is made in c it is not ready

Arguably, the real money is made in JavaScript and Python for the last decade. Embedded roles generally have fewer postings with lower pay than webdev. Until C catches back up, is it also not ready?