term.js

This brings back memories. I haven't looked at it in a while, but I'm glad to see the fork[1] of my fork[2] from 12 years ago is still thriving. Looks like it's been mostly rewritten. Probably for the better. [1] https://github.com/xtermjs/xterm.js [2] https://github.com/chjj/term.js

Hi all, I'm one of the maintainers of xterm.js, open to answer any questions! Here's a little history on the project, some of which is already called out in other comments: - Fabrice Bellard created jslinux[1]. - Christopher Jeffrey (@chjj) forked the terminal component into term.js[2], this eventually became unmaintained. - Paris Kasidiaris (@parisk) forked it into xterm.js for use in SourceLair[3]. - I showed up around 2016 when investigating options for VS Code's integrated terminal and eventually joined as a maintainer, spending a good deal of my time at work on the project since then. We currently have 5 active maintainers in the xterm.js team as well which I'd like to call out because the project has only come this far as a result of everyone's efforts. [1]: https://bellard.org/jslinux/ [2]: https://github.com/chjj/term.js [3]: http

term.js was originally created by Fabrice Bellard -- see the headers of @chjj's term.js file [1]. Bellard wrote term.js since he needed a way to interact with his amazing port [2] of Linux to a web browser. Term.js had a non-open-source license and @chjj spent time a decade ago successfully convincing Bellard to relicense term.js open source (I watched and greatly appreciated this as it happened!). Xterm.js is a very significant rewrite and improvement of term.js, mostly done by Daniel Imms who is on the VS Code team at Microsoft; xterm.js is a great contribution of Microsoft to open source, and is used at VS Code's terminal. I watched all this happen over the years, visited Daniel at Microsoft, etc.; I think this is all very useful tech (e.g., we use it in JupyterLab and CoCalc). [1] https://github.com/chjj/term.js/blob/master/src/t

This isn't even a decent terminal emulator in the basic ways. It has an enormous memory footprint, abysmal compatibility, and very little in the way of novel features to offer. If you use a better shell (like fish) it leaves this even less appealing. I'm sure this took some work to do, but I don't know anyone with a job to pay for it, which would use it. The word "efficient" describes the exact opposite of what this is. In addition to all of that, the package includes all of the build-time dependencies with it. And the package they use for the terminal emulator part of it is explicitly abandoned by its author (https://github.com/chjj/term.js/) Nobody should pay 10 dollars(let alone 20 dollars for limited ongoing support) for more than half a gigabyte of unmaintained, deprecated open source code, plus about 2000SLOC of proprietary code for

I find the timing of this amusing—I was just, in putting the finishing touches on my own project <tty-player> which is basically <video> but with ttyrec scripts for src, writing down my analysis of all the different options there are out there, and I saw this entry up here just as I was writing about asciinema. asciinema’s player has the distinction of being the only one I know of not based on term.js (https://github.com/chjj/term.js).

Well, you could go all out, grab https://github.com/chjj/term.js, plug that into termui using WebSockets or something, and it would most likely work: On the other hand, you can easily code your own without too much hassle. https://github.com/rcarmo/raspi-cluster includes a minimalist Dashing clone with a Go backend and real-time updates.

I've been meaning to try something like this at work for training and documentation. Haven't yet, but here's the previous discussion of showterm: https://news.ycombinator.com/item?id=6190600 A couple of interesting repositories mentioned in that discussion: https://github.com/chjj/term.js https://github.com/chjj/tty.js There was also mention of ascii.io (currently unreachable) and shelr.tv (domain squatter).

These are handy when you are stuck on a connection that blocks everything but HTTP(S), like many corporate environments. Many of these web-based ssh tools are based of the excellent term.js[0]. [0]: https://github.com/chjj/term.js

tty.js[1] works on windows (the backend is linked to the winpty library). I'd normally feel like I'm tooting my own horn by inserting this here, but it looks like the clientside part of Butterfly is a fork of my term.js[2]. I'm not sure if python's implementation of pty's handles some kind of workaround specifically for windows. [1] https://github.com/chjj/tty.js [2] https://github.com/chjj/term.js

Combine that with Term.js[1] and you could have a fully functioning terminal in the browser. [1] https://github.com/chjj/term.js

Author of term.js/tty.js[1] here. Nice work. You guys should keep an eye on term.js. The version you're using is slightly old and actually contains a bug (now fixed) wherein all events will become unbound if the reset control sequence is received. I'm also adding fixes for a few other things currently, such as double-width character support, which has been a problem in the past. [1] https://github.com/chjj/term.js