macpine VS Mosh

I recommend having a look at [1] which allows you to run lightweight alpine VMs on MacOS with easy port forwarding, file sharing, and you can easily run docker inside of it and use docker context to target it.

[1] https://github.com/beringresearch/macpine

I don't see the point of a dedicated tool for this when it is easy enough just to start a Alpine docker container with a couple commands. As this project is just a wrapper for docker and LXD[1] and those tools are already easy enough for the average SWE to interact with, the project seems to just over-complicate an already existing workflow.

[1] https://github.com/beringresearch/macpine#motivation

It uses almost same mounting tech as colima (9p)

Macpine: https://github.com/beringresearch/macpine/blob/71788e9c3c09c...

colima: https://github.com/abiosoft/colima/blob/7ebcf14a69158afa43b2...

So it seems that it has same performance as colima project as well.

As for IO performance, see this colima issue https://github.com/abiosoft/colima/issues/146#issuecomment-1...

If you haven’t already, and I know this doesn’t hold up for GUI emacs or vim, but consider running them through https://mosh.org/

FWIW, I wouldn't try to parse escape sequences "directly" from the input bytestream -- it's easy to end up with annoying bugs. Longer-term it's probably better to separate the logic e.g.:

- First step (for a UTF-8-input terminal emulator) means "lexing" the input bytestream as UTF-8 into a stream of USVs, which involves some subtleties (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- Second step is to run the DEC parser/FSM logic on the sequence of USVs, which is independent of the escape sequences (https://vt100.net/emu/dec_ansi_parser ; https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- And then the third step is for the terminal to execute the "dispatch"/"execute"/etc. actions coming from the FSM, which is where the escape sequences and control chars get implemented (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

Without this separation, it's easier to end up with bugs where, e.g., a UTF-8 sequence or an ANSI escape sequence is treated differently when it's split between multiple read() calls vs. all in one call.

Btw, you can use mosh to hide the latency of SSH. https://mosh.org/

I've been using Kitty's SSH features for as long as I can remember but I recently setup Mosh and I really like how it doesn't drop connections and supports roaming.

I am surprised many people write about ssh into a server. Mosh[1] feels more responsive and it also supports longer sessions.

[1] - https://mosh.org/

Also they support Mosh which I install on my servers. It's way better than plain ssh when you're on mobile networks and wifi, especially with connections that are unreliable or bandwidth-constrained.

I’ve recently been experimenting with MoSH (Mobile Shell). Basically think SSH but with UDP - so more resilient to shoddy network conditions, roaming access points, etc.

If it is not for production (e.g. running as a daemon or a server) and you only care about the development, another ad-hoc way is using screen/tmus-like software incl. byobu, and combine it with mosh.