- 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.
- I thought that there was a name clash: https://web.archive.org/web/20071010015641/https://martin.an... but I can't actually remember what that that wterm was. Not the same I would imagine. (edit: what I was thinking about was https://sourceforge.net/projects/wterm/)
- 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.
by jerrythegerbil
0 subcomment
- It you’re seeking something a bit older and battle tested ttyd is a good comparison:
https://github.com/tsl0922/ttyd
- It's compiled to wasm for "performance", but...
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...
by analogpixel
0 subcomment
- for a second I thought it was going to give me a filesystem view of the DOM of the webpage with unix utilities to ls/grep/find stuff. that would have been fun (although i'm not 100% sure the use.)
I was going to have Cluade do this, but I'm not sure if this is worth the tokens.
by williamstein
2 subcomments
- Wow, finally an alternative to xterm.js?
by Courfeyrac
0 subcomment
- [dead]
- [flagged]