I'm a recently-retired software engineer who focused on web browser development and web standards. I'm only starting to figure out what's next.
You may know me from my work on JavaScript promises and modules, streams and other WHATWG standards, custom elements, or the navigation API. Most recently I worked on speculative loading for web performance, and built-in AI APIs to expose the browser or OS's AI models to web developers.
I'm passing the time before the singularity hits by exploring Tokyo, where I moved in 2022. I spend a lot of time trying to learn Japanese, as well as keeping up with the latest in AI capabilities and safety research. I also maintain the jsdom open-source project. In a past life, I did physics research.
FavoritesWhat if your mind is nothing more than evolving data—and what if the cosmos is nothing more than a static mathematical object?
An introduction to the extensible web manifesto, a web API design philosophy that espouses exposing primitives and letting developers build high-level abstractions that are competitive with those shipped with the browser.
The original essay that helped promises win over callbacks in the JavaScript ecosystem.
Designing JavaScript streams APIs for network sockets, on top of non-blocking syscalls, leads us to the concept of push vs. pull sources.
Designing JavaScript streams APIs for file I/O leads us to consider bring-your-own-buffer APIs and how to avoid race conditions.
The intro to a short series of posts explaining some design decisions behind the web streams APIs, and how they abstract over underlying I/O interfaces.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.5