MAMara Averickinstdlib.hashnode.dev·3d ago · 3 min readThe 2026 stdlib community survey is openWe closed our last post, on a hundred interviews, by admitting that "a project's confidence about its users and a project's evidence about its users may be close to unrelated quantities"—so rather tha00
MAMara Averickinstdlib.hashnode.dev·Sep 3 · 15 min readLessons learned: 100 interviews about numerical JavaScriptWe ran a hundred customer-discovery interviews in seven weeks earlier this year, reaching out to anyone we could think of who might have something to say about high-performance numerical and scientifi01J
MAMara Averickinstdlib.hashnode.dev·Aug 24 · 35 min readWrite It Like C: What V8's Optimizing Compilers Explain About the Zen of stdlibJavaScript wasn't designed for numerical computing. There's one number type (a 64-bit float), no operator overloading, no control over memory layout, and a value model where every integer is, in princ00
MAMara Averickinstdlib.hashnode.dev·Aug 12 · 11 min readYour AI Policy Doesn't Have to Apply to YouA confession: stdlib doesn't have an AI-use policy. It isn't for lack of trying. There's an open RFC proposing guidance on AI usage—citations to prior art, disclosure requirements, a carve-out for "go00
MAMara Averickinstdlib.hashnode.dev·Jul 23 · 14 min readDo you WANT contributors?My open-source origin story goes something like this: I fixed a typo, tweeted some stuff, tripped, fell, and found myself in the inner circle of a large-scale OSS ecosystem with an active, supportive 00