@DrWhax the general consensus seems to be that this is not considered a problem. using 3rd party packages is easier than in c/c++, so there are fewer giant frameworks and less "everyone reimplements the same stuff over and over again". instead you just have more small packages. also, the standard library is intentionally small in order to reduce the maintenance burden and avoid a future choice keeping technical debt or introducing breaking changes.
@guenther but but what about an tcb?
@DrWhax about what?
@guenther a trusted computing base, how am I supposed to give any guarantees for so many dependencies?
@DrWhax Rust doesn’t have the problems node / npm does, as far as I can tell. The std crate is much more powerful, so you don’t need crates like isNumber or isEven.
@DrWhax @minoru @guenther @friend @stchris @bugaevc
I think this is a really nuanced topic.
potentially 100 authors you have to trust:
well, do you trust your own code, when you have to reimplement things that some people have probably already thought more carefully about? I wouldn't.
Instead of looking at the number of dependencies, I'd rather look at what *kind* of dependencies are used: are they still maintained, do they have unit tests, are they widely used in other libs etc.
1/2
@DrWhax @minoru @guenther @friend @stchris @bugaevc
I think that these metrics are much more important.
In general I lean much more to the "use a lib" and "don't reinvent the wheel" side:
https://blog.sindresorhus.com/small-focused-modules-9238d977a92a?gi=38ebfff51d3d
However, if you have very special requirements, it might make sense to not use a lib and implement it yourself.
There is so much more to say - this doesn't fit all in some toots 🐘
2/2
Server run by the main developers of the project 
It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!
@DrWhax Could you please give examples, so that we can evaluate it properly.
Thanks.