Sign in

stdlib

@stdlib.io
34 followers 62 following 14 posts

A standard library for Node.js and JavaScript which accelerates array and tensor computation in web applications. stdlib.io

PostsRepliesMedia
stdlib @stdlib.io · 04/09/2026
Shoutout to @dataandme.bsky.social for spearheading the interview effort and the write up!
000
stdlib @stdlib.io · 04/09/2026
📣 New post up on the stdlib blog! This one covers lessons learned after doing 100 interviews with a variety of stakeholders interested in numerical #javascript. Check it out and let us know your thoughts! blog.stdlib.io/lessons-lear...
blog.stdlib.io
Lessons learned: 100 interviews about numerical JavaScript
What a hundred interviews about numerical JavaScript revealed about how projects misjudge their own users.
111
stdlib @stdlib.io · 26/08/2026
Shoutout to @dataandme.bsky.social for another superbly written post! 🙌
011
stdlib @stdlib.io · 26/08/2026
V8, the JavaScript engine in Chrome and Node.js, has influenced a number of our design decisions. In this post, we discuss those decisions & explain why we do some of the things we do. The lessons are not exclusive to V8, being generally applicable to all JS engines. blog.stdlib.io/write-it-lik...
blog.stdlib.io
Write It Like C: What V8's Optimizing Compilers Explain About the Zen of stdlib
What V8's optimizing compilers explain about the Zen of stdlib—and why write it like C actually works.
131
stdlib @stdlib.io · 26/08/2026
📣 New post up on the stdlib blog! There has been a lot of talk regarding AI policies, whether OSS projects need them, and what they should include. In this post, @dataandme.bsky.social explores whether the choice is as binary as it seems. blog.stdlib.io/your-ai-poli...
blog.stdlib.io
Your AI Policy Doesn't Have to Apply to You
Not applying your own rules to yourself isn't always hypocrisy. Sometimes it's just correct.
011
Reposted by stdlib
Athan Reines @areines.bsky.social · 08/08/2026
Does JavaScript really need another plotting library? Probably not. But scientific JavaScript needs something different. We're building plotting for ndarrays, REPLs, servers, browsers, and the command line, all on top of Vega. Here's why: blog.stdlib.io/why-another-...
blog.stdlib.io
Why another plotting library?
Why another JavaScript plotting library? Learn what we're building for scientific computing and data analysis—and why.
061
stdlib @stdlib.io · 07/08/2026
AI agents learn from more than prompts. They learn from examples already in your repository. @anandkaranubc.bsky.social explains why consistency is infrastructure and why every stale convention is a wrong answer waiting to be copied. blog.stdlib.io/the-codebase...
blog.stdlib.io
The Codebase is the Prompt
Every inconsistency in your repository is a bug in the specification you are handing your AI agent.
131
stdlib @stdlib.io · 06/08/2026
We've been taught that being indispensable is a sign of success. In open source, it can also be a liability. The healthiest projects aren't built around heroes. They're built so that others can eventually take the work farther than we could alone. blog.stdlib.io/build-for-in...
blog.stdlib.io
Build for Inheritance
Building for inheritance means ensuring others can carry on the work of open source without you and thrive in your absence.
052
Reposted by stdlib
Mara Averick @dataandme.bsky.social · 23/07/2026
Not every open-source project wants more contributors right now, and that's fine. Four shapes maintainers run — walled castle, clique, university, hippie commune — and your `CONTRIBUTING.md` is saying the quiet part out loud. No wrong answer, just an honest one. blog.stdlib.io/do-you-want-...
blog.stdlib.io
Do you WANT contributors?
Four ways to run an open-source project—castle, clique, university, commune—and which one you're really running.
36617
stdlib @stdlib.io · 20/07/2026
Most people still think of browsers as thin clients. They're not. Modern browsers can run scientific computing, ML, and GPU workloads locally with no servers and no data leaving your device. A post by @gunjjoshi.bsky.social explains why that changes everything: blog.stdlib.io/the-largest-...
blog.stdlib.io
The Largest Compute Platform on Earth
Browsers can run machine learning and GPU-accelerated workloads locally. Here's why that changes everything.
152
stdlib @stdlib.io · 08/07/2026
Open source doesn't survive because the install gets smoother. It survives when users feel invited to become caretakers. We wrote about the Stakeholder Journey and the hard, human work of turning use into commitment. blog.stdlib.io/the-stakehol...
blog.stdlib.io
The Stakeholder Journey
A bowtie-shaped map of how open-source contributors move from first discovery to ecosystem leadership.
021
stdlib @stdlib.io · 27/06/2026
A tool for mapping your #opensource ecosystem and its saboteurs: The Ecosystem and Stakeholder Map. blog.stdlib.io/mapping-your...
blog.stdlib.io
Mapping Your Ecosystem (and Its Saboteurs)
Naming everyone in your open-source ecosystem—both competitors and colleagues—and following where value flows.
062
stdlib @stdlib.io · 17/06/2026
A surprising thing we learned when mapping our community: the people who contribute to an open-source project aren't always the people who use it. This post from @dataandme.bsky.social explores the Open-Source Ecosystem Canvas & the questions it surfaced for stdlib. blog.stdlib.io/open-source-...
blog.stdlib.io
The Open-Source Ecosystem Canvas
An ecosystem canvas makes an open-source project say who it's really for. Here's what ours surfaced about stdlib's value propositions for contributors and users—and why they're not the same.
031
stdlib @stdlib.io · 08/06/2026
For years, open source communities relied on visible friction: people got stuck, asked questions in public, and became part of a community. AI is changing that. What happens when newcomers are no longer visible—and neither side knows the other is there? blog.stdlib.io/ai-and-the-i...
blog.stdlib.io
What We're No Longer Seeing: AI and the Invisible Newcomer in Open Source
How AI is absorbing the visible friction that open-source communities have always relied on to see—and welcome—newcomers.
12411
stdlib @stdlib.io · 12/05/2026
We're excited to share stdlib's 2026 Google Summer of Code cohort! This year, we were awarded 5 contributor slots. The projects span machine learning, LAPACK/BLAS, and scientific visualization for the web. Huge thanks to everyone who contributed and applied! blog.stdlib.io/gsoc-2026-se... #GSoC
blog.stdlib.io
GSoC 2026 Selected Projects
We're thrilled to share that stdlib will have five contributors participating in Google Summer of Code 2026.
011
stdlib @stdlib.io · 09/05/2026
Today we're publishing the "Zen of stdlib": a philosophy of simplicity, modularity, consistency, and craft, which guides stdlib's development. If you're interested in scientific computing, library design, or sustainable software engineering, we think you'll enjoy it. blog.stdlib.io/zen-of-stdlib/
blog.stdlib.io
Zen of stdlib
A philosophy of simplicity, modularity, consistency, and craft.
141
Reposted by stdlib
Quansight @quansight.com · 30/09/2025
Happy International Podcast Day! 🎙️ Celebrating with some amazing episodes featuring our @quansight team: 🎧 Athan Reines on stdlib 🎧 Marco Gorelli on Narwhals 🎧 Ralf Gommers on NumPy 🎧 Travis Oliphant on SciPy & scientific Python Links 🧵👇 What's your favorite tech podcast? Share with us!
122
Reposted by stdlib
Quansight @quansight.com · 30/09/2025
Athan Reines explores JavaScript's technical computing with stdlib -https://buff.ly/50WOdgF
buff.ly
An insider’s view on the heart of NumPy: a conversation with Ralf Gommers - Inspiring Computing
In this episode, I have a wonderful conversation with Ralf Gommers, a director of Quansight Labs, and he's a key contributor to NumPy. He shares his journey of how he started working on and…
132
Reposted by stdlib
Philipp Burckhardt @burckhap.bsky.social · 17/07/2025
Read the full blog post here: blog.stdlib.io/reflection-o...
blog.stdlib.io
Using AI in the development of stdlib
A reflection on stdlib's participation in the 2025 METR study on AI's impact on open-source developer productivity.
062