tab-rs VS wasmer

If you want to read some code, my project is tab-rs.

I myself use the many (alacritty) terminals + tiling WM solution at the moment (switching between i3wm and LeftWM) but it doesn't feel optimal. I always though tmux looked too involved to learn so I've been on the lookout for alternatives such as Wezterm (a terminal with built-in multiplexing), tab (a command line controlled multiplexer) and now zellij.

Plus a lot of cleanup in the tab-pty-process crate. It now exposes an interface similar to portable-pty, but with non-blocking file handles.

I ended up writing a terminal multiplexer because screen and tmux were too complicated to use. It has a built in fuzzy finder, stateless navigation, and YAML configs for persistent sessions: https://github.com/austinjones/tab-rs/

The way I typically unify messages is define an enum, and map/merge channel receivers. tokio-stream would probably work with these examples. Here's an example from a fuzzy-finder implementation: https://github.com/austinjones/tab-rs/blob/main/tab-command/src/service/terminal/fuzzy.rs#L332

Really nice cheat-sheet write up on screen & tmux & byobu.

Also worth checking out tabs-rs[1] which seems very well reviewed & recent.

Personally, I am a huge fan of dtach[2][3], which isn't a multiplexer, just a detachable proxier of terminal sessions. This let's me run a persistent vim session that I can reconnect to, and vim has however many terminals I need open in it. Vim does my multiplexing, dtach just allows me to make vim persistent. Very glad to have re-discovered dtach, to enable this workflow.

Notably dtach is very lightweight. Unlike tmux, it is not a virtual terminal. Upon reconnect to my vim session, I issue a control-l to refresh the screen. Dtach hasn't retained the screen state, isn't translating between terminfos. The one thing that can go wrong here is connecting from different terminals- few programs have a way to update the TERM setting once the program has launched.

[1] https://github.com/austinjones/tab-rs

[2] https://github.com/crigler/dtach

[3] https://wiki.archlinux.org/index.php/Dtach

The nice thing about that is that many other tools can work too. Someone using direnv can set properties that would be available in the hurl script. Likewise, someone using tab could have environment variables defined for their active tab that could be used. If you invent your own notion of an environment, you lose interop with a lot of other tools that target the standard environment.

Are you running v0.5.3? I just released a fix for a Kakoune issue that was caused by add-highlighter global/ number-lines -relative in kakrc. It sounds similar to what you described.

There are also some crazy ANSI sequences that cause the terminal emulator to write stdin - so applications can query the terminal state. Crazy stuff can happen when those sequences are copied from the scrollback buffer (which is why tab now filters them out).

This is awesome. I'd love to have upstream support in Wasmer ( https://wasmer.io )

WebAssembly is extremely portable. WebAssembly runs on: all major web browsers, V8 runtimes like Node.js, and independent Wasm runtimes like Wasmtime, Lucet, and Wasmer.

Unfortunately cosmopolitan wouldn't work for dockerc. Cosmopolitan works as long as you only use it but container runtimes require additional features. Also containers contain arbitrary executables so not sure how that would work either...

As for WASM, this is already possible using container2wasm[0] and wasmer[1]'s ability to generate static binaries.

[0]: https://github.com/ktock/container2wasm

[1]: https://wasmer.io/

I could not find any guide how to add WASM container capability to Docker running on Colima. This guide provides a few Colima templates for exactly this, which adds WasmEdge, Wasmtime and Wasmer runtime types.

Just suggested as well Wasmer on Twitter! https://github.com/wasmerio/wasmer

Looking forward to seeing the results :)

The Biome team has been incredibly fast on solving the challenge and achieving 95% compatibility with Prettier [1]

Just as a note, as it was not mentioned in the article, Wasmer [2] also participated with a $2,500 bounty to compile Biome to WASIX [3], and it has been awesome to see how their team has been working to achieve this as well... hopefully we'll get Biome running in Wasmer soon!

Keep up the great work!!

[1] https://github.com/biomejs/biome/issues/720

[2] https://wasmer.io/

[3] https://wasix.org/

It's funny how WebAssembly can help overcome most of the issues mentioned on the blogpost (packaging, configuration, portability) if addressed properly.

That's the main reason Wasmer [1] was created :)

[1] https://wasmer.io

Thanks for the mention to Wasmer.

I'll put here a link in case is useful for future readers: https://wasmer.io/