Maybe this is why I'm a little skeptical of the whole "move everything to Rust/Zig/Go/etc" movement in the JS ecosystem. I like JavaScript, I understand JavaScript. If I have to debug some JS tool, I'm well-equipped. Whereas if I have to dip down into some weird error like "libfoo.so.42: cannot open shared object file" then I know I'm gonna get lost.
Plus I don't think we've come close to exhausting all the ways to optimize JS deps: https://marvinh.dev/blog/speeding-up-javascript-ecosystem/
@nolan personally, I prefer my tools forcing me to learn a language. That's how I learned JS to begin with. Tho, for terminal stuff, there's more variety of languages than JS, which is rather inconvenient.
And even then, going back to your first post, we still deal with OS issues such as directory conventions, permissions, and environment variables. I understand why you don't want language specific issues on top of all that 