Today’s JavaScript, from an outsider’s perspective (2020)

Re:Today’s JavaScript, from an outsider’s perspective (2020) by IshKebab on Friday May 27, 2022 @05:29AM (#31527614)

I don't think the Rust team are unaware of supply chain attacks, so you don't need to warn them. It's just that there's no easy solution. Or do you have some easy solution they aren't doing. Just to pre-empt you, namespacing doesn't solve the issue and manually vetting authors/crates is not something the Rust community wants.

[ Parent | on HN ]

Re:Today’s JavaScript, from an outsider’s perspective (2020) by reificator on Friday May 27, 2022 @11:48AM (#31530989)

Namespaces do not solve the issue but they do mitigate a specific vector, while also removing a perceived need to preregister crates.

There’s no downside beyond “it requires development time and maintenance” like any other feature.

[ Parent | on HN ]

Re:Today’s JavaScript, from an outsider’s perspective (2020) by IshKebab on Friday May 27, 2022 @12:47PM (#31531726)

What vector do they mitigate? And why would they remove the perceived need to preregister crates (or namespaces)?

[ Parent | on HN ]