[flerovium]

2. Ok, it's not xterm. What is the VNC server/client? I don't see on in the code. When you use replit, what will cause it to trigger a magic VNC client? What if I want to try a different VNC server to speed it up? When will the VNC close...there's a lot of magic that I as a developer can't really work with and doesn't seem to be documented.

AFAICT, this demo is equivalent to, "someone ran VICE in a VNC". I think that's the OP's point.

It isn't even clear what VNC (or what its performance profile is).

[19wintersp]

It's "magic", yes. Replit is not for you to mess around with the VNC or anything, that directly defeats its purpose. Replit is not a framework for building a Replit-like system. Replit is effectively just a way for you to save and interact with VMs in the cloud from your browser.

The whole point of this demo is "someone ran VICE on Replit". The VNC is completely besides the point.

[piemadd]

1. it is xterm, xterm.js to be sepcific 2. uses no-vnc. if you own the repl theres a way to set the vnc server password and access from your own client, but i forget how. probably on the replit docs/blog

[flerovium]

I think the x64 isn't xterm. It's not clear what the client is (or what errors if throws if it breaks).

[19wintersp]

Again, let me stress this: xterm.js is providing the console only. Any visual things, including the x64 window, are provided by the VNC connection, which is completely independent of the xterm console.

[flerovium]

Exactly, it's not clear what VNC is being used.