You are incorrect, though. The reason people advertise tools as being written in Rust is because having tools written in Rust tend to scratch a few itches that a lot of people have: speed, the fact it is native, the safety due to the borrow checker, the ease of installation, the ease of contribution, the possibility to learn something from the code, among other things. Those things matter a lot to me, and I assume to a lot of other people.

I am probably going to look into it, since I'm often annoyed by npm run as well. However if it were in another language I don't want my tools written in, I would probably pass. Something being in a certain language is not a guarantee that it will be great, but being in others is often a guarantee that it isn't. Which language tools are written matters a lot to me.

I understand how all this might look like to someone "out of the loop", however, but I wouldn't be too quick to judge other people.

Dismissing a project out of hand because it's written in a certain language because it's trendy is the same faulty logic than choosing a certain language for a project because it's trendy.

> ... I'm less likely to choose it, ...

I find I am more likely to choose it because you don't have to be super experienced in Rust to produce fast, reliable binaries. That is not the case with C/C++.

Except this is written in Rust because the author wanted to learn Rust.

> I want to try and learn Rust so I made this. Inspired by bun.