upp-components VS contour

Terminal Package for U++ - U++ framework - Linux, OS/X, Windows

Another problem is that the cursor moves while the screen is buffer is being rendered. The location is only really known once the cursor settles in the same place for some time, which is unacceptable in terms of latency.

The synchronized output extension could be used to do this, though. https://github.com/contour-terminal/contour/blob/master/docs...

https://github.com/contour-terminal/contour/issues/382

This apparently does not support the Kitty graphics protocol, just Sixel, which makes it look fairly unattractive to me, personally.

contour - https://github.com/contour-terminal/contour. https://github.com/contour-terminal/contour/issues/100 and other modern unicode focused attempts to update the terminal world

contour : a terminal application

https://github.com/contour-terminal/contour Contour has a implementation for this. See this release: https://github.com/contour-terminal/contour/releases/tag/v0.3.6.240

Now that I'm well rested I decided to compile some similar terminal emulators with clang++ and rustc to see how big of a gap we're looking at. For the C++ terminal emulator I compiled contour with ~80k lines of C++ and over 200k lines when accounting for dependencies (not including dynamically linked dependencies), and then I'm using alacritty with ~35k lines of Rust and over 2 million (!) lines for the whole dependency tree when vendoring all dependencies. Because Rust tries to make most software cross platform with conditional compilation and many of these aren't Linux specific libraries I'm gonna assume it's compiling half or two thirds of the lines of dependencies for this experiment with the C++ compiling probably 3/4ths of the dependency tree considering I'm not on windows.

I have my eyes on this though.