JS Party: JavaScript, CSS, Web Development · Changelog Media

A standard library for JavaScript

·51 min·3 clips

The project was designed to avoid external dependencies and supply-chain risk by building everything in-house.

1. JS Party talks with Philip Burkhardt about stdlib.io, the standard library for JavaScript. 2. Philip Burkhardt is the author of stdlib.io, and he says he has a PhD in statistics and data science. 3. The episode asks why JavaScript still needs a separate standard library when the language already has npm and modern runtimes. 4. Philip says many data science jobs are really data engineering jobs centered on ETL, extracting, transforming, and loading data. 5. He argues that the hardest part of working with data is often getting the data into the right format and checking for hidden issues. 6. The hosts ask whether LLMs can clean up dirty CSVs, and Philip says they can help but can also introduce other errors. 7. He gives a concrete use case where LLMs are useful for unstructured text, website scraping, and converting content into JSON. 8. Philip says stdlib started from a need for a rigorous set of tools that would not depend on external tooling or dependencies. 9. He says the library aims for high-quality code, full documentation, and code coverage so users can depend on it over time. 10. He explains that the project focuses on numerical and statistical computing infrastructure, but it also covers general utilities and natural language processing tasks. 11. Philip says the library now has roughly 3,800 GitHub repositories because each package is generated and published separately. 12. He says users can install individual packages from npm or consume namespaces that group statistics or special math functions together. 13. He describes the library as fully decomposable, with package-level dependencies managed through Node.js module resolution and generated package.json files. 14. Philip says the team publishes CommonJS to npm right now, while also generating ESM and Deno bundles for other consumers. 15. He explains that the project stays conservative about new JavaScript features because backward compatibility and predictable performance matter. 16. He says the library avoids patterns that hurt compile optimization and tries to keep argument types stable for runtime efficiency. 17. Philip and the hosts keep the tone technical and pragmatic, with repeated comparisons between old JavaScript habits and newer tooling. 18. The conversation stays interview-based and exploratory, with long explanations about architecture, packaging, and maintenance. 19. Listeners who build data tools, JavaScript libraries, or large package ecosystems will get the most from it. 20. People looking for a lightweight JavaScript news recap or a short general-audience chat may skip it.

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from JS Party: JavaScript, CSS, Web Development