blink VS Mosh

you can work on it

https://blink.sh/

see also https://docs.blink.sh/advanced/code

Fixes for the new OS, general improvements, and tons of thanks to all testers for their help! https://github.com/blinksh/blink/discussions/1850

You can already do that with an iPad (sans fat OS). If you're using Blink Shell (https://blink.sh) the external display is independent of what's on the iPad too, which works really neatly. This is the exact setup I used as my main dev machine in a previous role.

Would be very nice to see if this works on the new iPhones. A thin client with decent security in your pocket with keyboard/mouse/display at both home and work seems like a very approachable computing setup.

I use blink[0] with a 40% keyboard to develop linux program on a vps.

If you want to do programming without wireless interenet, another option is to connect a raspberry pi zero 2w (with usb gadget mode enabled) to the usb c port using a single usb cable. Then the rpi zero will share a ethernet network with iOS device. Then you can use blink (again) to mosh to raspberrypi.local to do the development on the pi.

The reason that I don't do it on android with termux is that there's no high quality terminal emulator like blink on android.

[0]: https://blink.sh

There's also Blink [1] which includes a local shell (limited), ssh and mosh support, and comes with a local-first, but remote-dependent, vscode implementation. Works with vscode.dev, code-server (the coder.com and microsoft version), coder.com etc. Not free but a free TestFlight versions available if you accept to be a beta tester of sorts.

I've had moderate success using it, but overall the code-server experience has been a bit lacking, in part due to languages I use, in part due to lots of software still assuming a local-first development environment (code-server/coder.com help with this by e.g. proxying http ports in your dev environment). A real IDE/code editor running on a MacBook is still way superior.

[1] https://blink.sh

If you're okay with a subscription model for a terminal type shell, I would recommend Blink. Does everything Prompt did and more. They have a 1-week trial, and then you can subscribe for $20 a year.

I also opened https://github.com/blinksh/blink/issues/1777 so from now on everyone is able to see the commit reference that was used for the build.

I took a wild stab at finding a non-subscription iOS app that supports Ed25519-sk, but ended up just moving back to ephemeral per-device ed25519 keys instead. Both Blink.sh and Terminus purport to support -sk / HW passkeys behind subscription paywalls, but I can't verify as I don't pay for subscription model apps.

Big fan of Blink, makes it super easy to quickly ssh into a remote machine

SSH or mosh (via https://blink.sh/) back to a cloud/remote NixOS VM. The iPad is purely a self-contained interface with a local browser.

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.