fix windows fullscreen rendering keyboard demo

[jbolda]

Motivation

The bottom of our demos were clipped around ~20px.

Approach

The full string wasn't being written out in windows, so we needed a loop to finish writing it.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/clayterm@34

commit: 4e2fb43

[cowboyd]

Yikes! Is there anywhere we can read up on the differences of fullscreen on windows?

[jbolda]

I was reading through this last night, but I haven't seen anything explicitly pointing to the issue, at least that buffered fullscreen write issue specifically.
https://learn.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences#alternate-screen-buffer

[cowboyd]

Hmmm. Nothing leaps out to me about how this might be different than the way other terminal emulators handle it. Maybe we can ask a robot why that fix works.

[jbolda]

Turns out it was slow IO on Windows with Deno (non-built / running directly) and Deno doesn't guarantee to write everything to stdout in a single call so we need a loop over it.

[jbolda]

As this has become more of an adjustment to an example, I am going to pull out the result of this work into a separate PR. We are going to adjust our examples now and in the future to only use the node: APIs which should resolve this issue (that API presumably writes differently). It will also make the examples runnable in node as well.

[jbolda]

Superseded. See #48.