1. WASM FFI has a big overhead when interacting with the javascript DOM.
2. Any DOM UI has a big overhead compared to a canvas.
I would be curious to see an actual performance evaluation. This looks like it was built for the wrong tradeoff otherwise...
With AI it's so easy to work on something for a couple days and make it seem production-ready before losing any interest and moving on to something else. I may be wrong but it seems like that's what is happening at Vercel Labs. Pumping out new radically different things, and seeing what sticks.
I wish such kinds of experiments clearly labeled what it was instead of trying to look production-ready. It coming from a big player like Vercel can especially inspire a false sense of trust, when it was just messing around with AI around some idea and then moving on.
https://github.com/coder/ghostty-web/
In fact, it looks like wterm's 12KB plugin doesnt offer full term emulation and uses ghostty to support everything else:
wterm ("dub-term") renders to the DOM — native text selection, copy/paste, find, and accessibility come for free. The core is written in Zig and compiled to WASM for near-native performance.
wterm ("dub-term") renders to the DOM — native text selection, copy/paste, find, and accessibility come for free. The core is written in Zig and compiled to WASM for near-native performance.