4 ms·
> Reinventing the wheel is error prone. Having a standard lib for these sort of functions is a common pattern many languages adopt.
by maest 5y ago
> Reinventing the wheel is error prone.
Having a standard lib for these sort of functions is a common pattern many languages adopt.
- MsMowz 5y agoIsn't that really a pattern that the runtime adopts (i.e. not the language itself)? For ES, the libraries are dependent on the runtime environment; for browsers, there are the web APIs, and for Node, there's npm. I'm not sure how you could have anything more standard given the nature of things.
- Quekid5 5y agoThis might be just a few levels of people talking past each other, but just in case: Yes, the full "standard libarary" you can expect to be present on any given JS VM may vary, but there's no plausible reason that e.g. at() should not work on almost any conceivable platform.
- tomstoms 5y ago> for Node, there's npm True, NodeJS runtime comes with its own «standard library» but npm has nothing to do with it.