> Just as web developers, of all people, are finally, after over a decade, coming to the conclusion that arbitrarily-packaged dependencies are a bad idea for so many obvious reasons, Rust developers are trying to replicate NPM in the kernel.
Web developers and Rust developers are the same group
I'm sure there are web developers that are also Rust developers and vice versa, but the vast majority of developers I know that belong to either of those groups don't belong to the other.
Given it was born at Mozilla, is getting traction at WebAssembly and WebGPU efforts, WGSL is loosely based on its syntax, and some Cloud Native projects are migrating from Go to Rust, I am quite sure there is some overlapping.
Not that I agree with Rust's adoption at that level, as I think languages with automatic memory management make more sense, but that's me.
What people are roundaboutly observing is that the vast majority of developers these days either begin their career or spend at least a part of their career as web developers. That Rust is such a successful onramp to systems development even for people who haven't been classically trained in it is one of the strengths of the language.
While it is good that such people are embracing Rust for such purposes, they would have had a similar high level experience with something like Modula-2 or Object Pascal.
If anything, it is the pseudo-macro Assembler approach to C's design that made it a scary experience for some developers.
"related to" is doing a lot of work there. Browsers are "related to" the web, but surely you don't think Mozilla, if hiring for someone to work on the CSS layout engine or something for Firefox in c++ or rust, would advertise for a "web developer". It's just not the same job in any way.
Web developers and Rust developers are the same group