Some comments comparing DomTerm (
http://domterm.org/) and Hyper2 (H2):
DT does not require Electron: There are also embeddings for Qt (using QtWebEngine), Atom, Theia - or you can use a desktop browser. If you use Electron, it is only used for the "chrome" (menus etc). The "backend" (server) is a C program. (It works great on Windows using WSL.) There is also a simplified pure-Java backend.
Hyper2 is clearly faster. Using canvas seems like a win in that respect, but I'm concerned this limits the ability to style the output using CSS. Using a more structured representation (e.g. DOM) also preserves valuable information about the output. The ideal might be to have a structured representation as "the truth" but render to a canvas. This might still be less flexible in terms of using CSS, but that might be an ok tradeoff.
Om H2, if you change the window width, wrapped lines are not re-calculated.
H2 does not "remember" tabs. I.e if you 'cat Makefile', and copy the output, you get spaces, not tabs.
H2 shows a lot more errors when running the vttest test suite.
DT supports hyper-links to file positions. For example clicking on FILENAME:LINE:COLUMN: (as produced by many compilers) will open a (customizable) editor and go to that position.
DT supports "printing" images, rich text, and general HTML.
DT supports tabs, draggable panes, detachable sessions (like tmux/screen), and a builtin input editor.