$ grep -r "WebAssembly" ~/blog/

The Web Audio API represents one of the most ambitious and controversial additions to the web platform. Designed to bring professional grade audio processing to browsers, it promised to enable everything from game audio engines to digital audio workstations (DAWs) running entirely in the browser. Nearly a decade after its initial release, the API has achieved widespread browser support and enabled impressive demonstrations. Yet beneath the surface lies a more complicated story: one of design compromises, unmet expectations, and fundamental tensions between different visions of what audio on the web should be.

This is not just another technical critique. The Web Audio API’s troubled history reveals important lessons about web standards development, the challenges of designing APIs by committee, and the sometimes painful gap between what audio professionals think developers need and what developers actually need.

DosKit

WebAssembly-powered platform enabling instant, one-click access to DOS software and demos directly in modern web browsers.

Live Demo

DosKit represents a fundamental shift in how we preserve and access computing history. By leveraging modern WebAssembly technology, it eliminates the traditional barriers to experiencing DOS software—no installation, no configuration, no compatibility issues. Just click a link and experience classic computing instantly in any modern browser.

The intersection of artificial intelligence and systems security has reached a critical inflection point. As AI agents become increasingly capable of executing external tools and accessing system resources, the traditional security models that govern software execution are proving inadequate. Microsoft’s Wassette emerges as a groundbreaking solution that leverages WebAssembly’s sandboxing capabilities to create a secure, scalable runtime for AI tool execution through the Model Context Protocol (MCP).

Wassette represents a paradigm shift from the current landscape of MCP server deployment, where tools typically run with unrestricted system access, to a capability-based security model that provides fine-grained control over resource access. This architectural evolution addresses fundamental security concerns while maintaining the flexibility and extensibility that make MCP valuable for AI system integration.