Grilled Cheese

ExploreLog inSign up

Athan Reines

@areines.bsky.social

65 Following94 Followers

Core developer of stdlib. Engineering manager at Quansight. PhD in Biophysics.

https://github.com/stdlib-js/stdlib

PostsRepliesMedia
@areines.bsky.socialSep 4, 2026, 1:04 AM

This isn't a plug, but we've developed and used github.com/stdlib-js/st... for 8+ years and have never needed anything more than the max rate, despite the fact that numerical/statistical computing is our entire thing.

github.comstdlib/lib/node_modules/@stdlib/bench/harness at develop · stdlib-js/stdlib✨ The fundamental numerical library for JavaScript and TypeScript. ✨                   ⭐️ Star to support our work! - stdlib-js/stdlib
@areines.bsky.socialSep 4, 2026, 12:59 AM

2c, but IMO, it makes similar mistakes to other benchmark tools and includes various statistical functionality which is not particularly robust or informative.

1
@stdlib.ioSep 4, 2026, 12:28 AMReposted by @areines.bsky.social

📣 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.ioLessons learned: 100 interviews about numerical JavaScriptWhat a hundred interviews about numerical JavaScript revealed about how projects misjudge their own users.
1
@stdlib.ioAug 26, 2026, 12:00 AMReposted by @areines.bsky.social

Shoutout to @dataandme.bsky.social for another superbly written post! 🙌

@stdlib.ioAug 25, 2026, 11:59 PMReposted by @areines.bsky.social

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.ioWrite It Like C: What V8's Optimizing Compilers Explain About the Zen of stdlibWhat V8's optimizing compilers explain about the Zen of stdlib—and why write it like C actually works.
1
@stdlib.ioAug 25, 2026, 11:50 PMReposted by @areines.bsky.social

📣 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.ioYour AI Policy Doesn't Have to Apply to YouNot applying your own rules to yourself isn't always hypocrisy. Sometimes it's just correct.
@areines.bsky.socialAug 8, 2026, 10:39 PM

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.ioWhy another plotting library?Why another JavaScript plotting library? Learn what we're building for scientific computing and data analysis—and why.
@stdlib.ioAug 7, 2026, 12:38 PMReposted by @areines.bsky.social

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.ioThe Codebase is the PromptEvery inconsistency in your repository is a bug in the specification you are handing your AI agent.
1
@stdlib.ioAug 6, 2026, 10:50 AMReposted by @areines.bsky.social

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.ioBuild for InheritanceBuilding for inheritance means ensuring others can carry on the work of open source without you and thrive in your absence.
@dataandme.bsky.socialJul 23, 2026, 3:19 PMReposted by @areines.bsky.social

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.ioDo you WANT contributors?Four ways to run an open-source project—castle, clique, university, commune—and which one you're really running.
3
@areines.bsky.socialJul 20, 2026, 8:03 PM

Yeah, there are definitely some rough edges with webgpu. Things are improving, albeit a bit slowly. As more use cases and needs arise, I expect this to accelerate capabilities. Tooling and infra definitely need to improve, which is something we have only just recently started exploring.

@stdlib.ioJul 20, 2026, 6:08 PMReposted by @areines.bsky.social

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.ioThe Largest Compute Platform on EarthBrowsers can run machine learning and GPU-accelerated workloads locally. Here's why that changes everything.
1
@areines.bsky.socialJul 18, 2026, 11:37 PM

Definitely in agreement here. And having followed the replacements repo for a while now, I can confirm that there are politics and lobbying at play with folks, including some of the maintainers, writing their own “nano” replacements and then advocating for their own utils over existing pkgs.

1
@nodeland.devJul 18, 2026, 12:52 PMReposted by @areines.bsky.social

github.com/npmx-dev/npm...

github.comWhy a Package Registry Should Not Be Picking Winners · Issue #3058 · npmx-dev/npmx.devMy understanding is that npmx aims to be "A fast, modern browser for the npm registry. Speed first, URL compatible, and simple", therefore, I think it should not be picking winners. If npm shipped ...
2
@nodeland.devJul 18, 2026, 12:32 PMReposted by @areines.bsky.social

A package registry should not be picking winners

10
@stdlib.ioJul 8, 2026, 10:03 AMReposted by @areines.bsky.social

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.ioThe Stakeholder JourneyA bowtie-shaped map of how open-source contributors move from first discovery to ecosystem leadership.
@areines.bsky.socialJun 27, 2026, 8:39 AM

That's awesome. And yeah, I have heard it is one of the taller ones. 😅

1
@stdlib.ioJun 27, 2026, 8:34 AMReposted by @areines.bsky.social

A tool for mapping your #opensource ecosystem and its saboteurs: The Ecosystem and Stakeholder Map.

blog.stdlib.io/mapping-your...

blog.stdlib.ioMapping Your Ecosystem (and Its Saboteurs)Naming everyone in your open-source ecosystem—both competitors and colleagues—and following where value flows.
@areines.bsky.socialJun 20, 2026, 10:43 AM

Wait...did you go off and hike Denali?!

1
@stdlib.ioJun 17, 2026, 4:19 PMReposted by @areines.bsky.social

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.ioThe Open-Source Ecosystem CanvasAn 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.
Older posts
Terms of UsePrivacy PolicyCommunity StandardsHelpGet the app

Grilled Cheese is a product of Village Compute

Version devBuilt at: 2026-10-12 02:39:10 EDT