Rethinking Boundaries in the JavaScript Ecosystem
In recent years, tools in the JavaScript ecosystem have evolved beyond their traditional roles. As individual tools take on a broader range of responsibilities, the boundaries between them are becoming increasingly blurred.
How much should a single tool take on, and what should it leave to other tools or to standards? How can we reconcile preserving compatibility with creating unique value, and technical progress with sustaining an open ecosystem?
In this panel discussion, our panelists will explore where the JavaScript ecosystem stands today and where it may be headed next, through the lens of the boundaries between tools, between implementations and standards, and between projects and communities.
Rethinking Boundaries in the JavaScript Ecosystem
In recent years, tools in the JavaScript ecosystem have evolved beyond their traditional roles. As individual tools take on a broader range of responsibilities, the boundaries between them are becoming increasingly blurred.
How much should a single tool take on, and what should it leave to other tools or to standards? How can we reconcile preserving compatibility with creating unique value, and technical progress with sustaining an open ecosystem?
In this panel discussion, our panelists will explore where the JavaScript ecosystem stands today and where it may be headed next, through the lens of the boundaries between tools, between implementations and standards, and between projects and communities.
Leo Kettmeir
I am a software engineer at Deno, where I've implemented key Web APIs—including WebSocket, WebGPU, and Web Storage—and contributed to core runtime features.
I focus on improving developer experience through tooling and documentation. Additionally, I am a maintainer to jsr.io, a modern alternative to npm, where I lead work on documentation tooling and registry infrastructure.
Leo Kettmeir
I am a software engineer at Deno, where I've implemented key Web APIs—including WebSocket, WebGPU, and Web Storage—and contributed to core runtime features.
I focus on improving developer experience through tooling and documentation. Additionally, I am a maintainer to jsr.io, a modern alternative to npm, where I lead work on documentation tooling and registry infrastructure.