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...
simjnd 1 hours ago [-]
All the commits and releases happened in an extremely short timeframe about a month ago and then nothing.
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.
kmaitreys 1 hours ago [-]
Probably some tokenmaxxing competition between the employees. The whole company seems under some kind of AI psychosis.
jerrythegerbil 19 minutes ago [-]
It you’re seeking something a bit older and battle tested ttyd is a good comparison:
Unfortunately the browser still can't make the kind of network connection needed to transport a terminal session to a remote computer natively. afaik all the tunneling solutions are pretty clunky/insecure.
theturtletalks 38 minutes ago [-]
Have you looked into VibeTunnel? I got the terminal working in my browser and it runs on my computer. I can access it on my phone since we’re on the same Tailscale network. I use Ghostty-Web and tried to switch to Wterm but it didn’t work. I think it’s because Ghostty-Web renders a canvas and wterm normal div tags.
jarym 1 hours ago [-]
What do you mean - WebTransport can do a lot...
Cloudef 51 minutes ago [-]
Lot but not enough still. Most web tech is like that, almost there but not really. Webaudio prob being the worst one. Webgpu being weird thing that nobody really knows who it is for.
williamstein 3 hours ago [-]
Wow, finally an alternative to xterm.js?
nacs 3 hours ago [-]
Ghostty-web exists and is even API compatible with xterm.js (same engine that powers Ghostty):
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/tsl0922/ttyd
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:
https://wterm.dev/ghostty