3 ms·
I'm very interested as to why this phenomenon - not having an authoritative way to vet third party libraries - seems to be a uniquely frontend concern. What hav
by tomlagier 8y ago
I'm very interested as to why this phenomenon - not having an authoritative way to vet third party libraries - seems to be a uniquely frontend concern. What have the dozens of other, battle-tested languages done to solve this? How do I know that a Maven package or Rust crate is legitimate, useful, and sans-malware?
It seems like this is a question fundamental to any programming ecosystem, that _must_ have a reasonable solution which balances developer time assessing a potential library with the utility of that library. I'm very interested in some strategies the JS ecosystem could take to foster a culture or platform with well-known, well-supported standard libraries.