Re:Jndi: An irresponsibly bad logging library
by monkeybutton on Saturday December 11, 2021 @09:12AM
(#29520968)
There isn't a benefit to OSS projects all competing for the same audience and bloated feature set. Picking a subset, being opinionated about it and the implementation isn't wrong. For developers, there is such a thing as picking the right tool for the job, even if it isn't your favourite one you usually use.
[ Parent
| on HN ]
Re:Jndi: An irresponsibly bad logging library
by mcfedr on Saturday December 11, 2021 @09:41AM
(#29521164)
As much as people moan about npm community, it does give you many choices and you can avoid complicated massive libs
Re:Jndi: An irresponsibly bad logging library
by Ygg2 on Saturday December 11, 2021 @04:51PM
(#29524595)
...By adding thousands of libs, turning node_modules into a multi GB folder. Oh, and each of which can be compromised by an unscrupulous actor.
Good luck auditing that.
Re:Jndi: An irresponsibly bad logging library
by p2t2p on Wednesday December 15, 2021 @02:37AM
(#29563083)
Like if any other thing with automatic package management is any better.
.m2/repository is 5 gb on my machine.
Rust crates?
Go packages that are neatly tucked away too?
Node just makes it visible and in your face by putting the node_modules in you project directory.
Besides, what’s the alternative? Write stuff yourself? Put stuff in language stdlib? Even minimal service requires _a lot_ of things to do minimal stuff.