| ▲ | pier25 2 hours ago | |
I agree and I also wish Node did more. Otoh should a standard lib give you absolutely everything? Probably not. There needs to be a line somewhere. Right now Bun’s policy on this seems to be "whatever Jarred feels like should be in there". | ||
| ▲ | erlich 2 hours ago | parent | next [-] | |
> "whatever Jarred feels like should be in there" This is the main draw. Everything he implemented was fast and minimalist and he usually implements a standardized api (web apis, esbuild bundler api). The opinionated stuff is usually very common sense. Most of the libraries OC mentions are things you would just like to be as fast as possible above all else. | ||
| ▲ | barnabee 29 minutes ago | parent | prev [-] | |
My line for exclusion from standard library is a library that’s any one of: - not obviously/generally useful (i.e. useless or too specific/should be a program not a library) - obviously trivial - already available (open source) elsewhere by a credible team that supporte and maintains it Anything else… put it in the stdlib | ||