▲ | skydhash 4 days ago | ||||||||||||||||
But why can’t we have a good library instead of those mini thingies? | |||||||||||||||||
▲ | progbits 4 days ago | parent | next [-] | ||||||||||||||||
For C++ there are Boost, Folly, Absl, several more large libraries with reputable orgs behind them. I'm surprised someone doesn't make a big npm lib like that. Not hating on the author but I doubt similar compromise would happen to Facebook or Google owned package. | |||||||||||||||||
| |||||||||||||||||
▲ | zahlman 4 days ago | parent | prev | next [-] | ||||||||||||||||
Because you have to figure out what should be in it, and coordinate the distribution. It's not like there's a reference implementation of JavaScript maintained by a well-known team that you consciously install everywhere that you need it. | |||||||||||||||||
| |||||||||||||||||
▲ | mhitza 4 days ago | parent | prev | next [-] | ||||||||||||||||
Because "look at how many open source packages I maintain!" At a time small JS libraries were desired, and good library marketing approach, but nowadays simple sites ship megabytes of without a care. In particular this developer is symptomatic of the problem of the NPM ecosystem and I've used him multiple times as an example of what not to do. | |||||||||||||||||
▲ | eviks 4 days ago | parent | prev | next [-] | ||||||||||||||||
Because a mini thing can be written in mini time by a mini number of people | |||||||||||||||||
| |||||||||||||||||
▲ | jamesnorden 4 days ago | parent | prev [-] | ||||||||||||||||
The JS ecosystem values quantity over quality, for some bizarre reason. |