isn't it kind of irritating to anyone else that dependencies discourse always ends at "trust nothing trust no one, have as few dependencies as possible and read every line yourself"
Conversation
ppl be like "we live in a society" until you have to participate in society
3
5
104
if you don't do anything you don't have a security risk! congratulations. we still have to do things. what's necessary to make "having dependencies" not a scary risk?
10
4
92
Replying to
Feature rich standard libraries help a lot with avoiding external dependencies. It's hard to avoid depending on lots of external libraries when writing Rust since the standard library doesn't cover much above low-level functionality. JavaScript is dramatically worse than that.
2
1
Having a fat standard library can also cause a lot of friction. Assuming that the core developers get everything right, then all is well, but the odds of that are quite slim, and once you add a feature, it becomes very hard to remove it.
2
The standards for stability aren't inherently different in the standard library compared to an external one. If most of the external libraries don't provide good backwards compatibility, then that's just further demonstrating that they aren't a replacement for a standard library.
The difference is that, when a better idea comes along, a new library can be created.
Just look at the Python community for a good example of this. A huge portion of the standard library sits gathering dust. The community has created replacements that work better.
1
A better library can be created as part of the standard library too. Python's standard library is very poorly maintained and they moved away from wanting to have a strong standard library. It's no longer an example of a project that's attempting to provide that at this point.
1
Show replies