The problem seems to be that they come at things from the wrong direction - you can&#x27;t run vim without being backwards compatible with at minimum terminfo pages, very likely vim also makes an assumption also that the terminal communicates over a tty, and possibly you may just need to support actual ANSI Escape Codes. You can&#x27;t run anything else without that either. Running vim should be the first thing this terminal can do.<p>Just like the web itself, any new teminal client needs to be backwards compatible with the capabilities of prior terminal clients, because programs that run in the terminal expect it. And if your terminal can&#x27;t run the programs everyone runs in their terminals, no one will adopt your terminal. But many of these projects seem to have no intention of maintaining that backward compatibility. Some, like TermKit, fully conflate the terminal and the shell and even many UNIX utilities.<p>You can&#x27;t hope to supplant ANSI compatible terminals when you let them have the enormous advantage of running all the software anyone wants to run in a terminal that already exists. It would be like saying you have a new, better web browser that can&#x27;t open any existing web pages.<p>No idea if this particular project has learned from past examples and is backwards compatible or not. (EDIT: It doesn&#x27;t have a terminfo page, so probably not.)