Actually, I found the homepage (landing page) not so great, and came here to the comments, in the hope to get some more information. Specifically, I use Mosh, and I would like to know, is this the same thing? If yes, how is it different? What are advantages/disadvantages? I would have wanted a more detailed comparison. The name is also a bit confusing; just from the name, I thought this might be a terminal emulator.
Back to Mosh: If it supports scrolling, how does that work? Is there also a prediction engine like in Mosh? What about ncurses apps? I skimmed briefly through the "how it works" page now, and it seems it also uses TCP instead of UDP. Shouldn't UDP be a better protocol for such a tool (also, that's what Mosh uses)? That page also does not say anything about how the prediction works (which is important in Mosh for the low latency), or whether it even does that (or how else could it have low latency)?
At least one of your questions is answered above the fold of the homepage.
mosh: Mosh is a popular alternative to ET. While mosh provides the same core funtionality as ET, it does not support native scrolling nor tmux control mode (tmux -CC).
My understanding is: Mosh can't scroll because it doesn't send you the full output of the terminal. It only sends you the current "window" (visible terminal contents) at the current time. ET sends you everything.
So if a program suddenly outputs a massive number of lines, mosh will discard the beginning and only send you the visible end of the output. ET will send you everything - which might bog down slow connections, but provides natural scrollback.
It appears that it just creates encrypted stream connection, ensuring that no data is lost when TCP reconnects.
So scrolling/all terminal functions works as with normal SSH.
Contrary to Mosh, which emulates its own terminal, synces whole screen so it doesn't clog with runaway output, works with high packet loss and have local typing prediction.
Back to Mosh: If it supports scrolling, how does that work? Is there also a prediction engine like in Mosh? What about ncurses apps? I skimmed briefly through the "how it works" page now, and it seems it also uses TCP instead of UDP. Shouldn't UDP be a better protocol for such a tool (also, that's what Mosh uses)? That page also does not say anything about how the prediction works (which is important in Mosh for the low latency), or whether it even does that (or how else could it have low latency)?